Lka1988

I love the command line. A terminal window is always open on whatever computer I’m using at the moment, even when I was running Windows.

But I also like having a dashboard to see what’s going on, all right in front of me. I have ADHD, and if I can’t see it, then I will forget it exists. I use command line to handle more granular tasks, and have various UIs to help me handle other things, like Proxmox (obvious), Dockge (docker stacks), OMV (NAS), Cockpit (all of my computers have this, really good for remote control), and a few other things I’m forgetting.

OP also has an XY problem.

Oh god, that… I recently realized that I’ve been fighting that concept with one of my cars for over a year now. Just this week, I finally figured out the right troubleshooting path 😂

OP also said they’re willing to learn the terminal:

I would like to find an OS that is easier to setup with less of a neccesity for the command line (I would still like to learn how to use it though, I don’t want to get rid of it entirely!).

They’re essentially asking to start with a working and well-known platform that any Joe Regular can use. In car terms, this would be akin to the Chevy 350 V8. Pretty much every car guy knows that engine and how to make it run well without needing to rebuild the entire thing right off the bat.

I’m all for command line, but I’m the kind of person who needs a dashboard, otherwise I forget everything. OMV has a solid dashboard and has been really good for me.

What’s so different between 1.22 and 1.23 though? I just updated my client to 1.23 because of this post and I see very little difference.

Yeah, so I’ve heard 😕

I use SMS Backup/Restore, it saved my ass during my divorce.

I’d love a FOSS version that can handle RCS…

Remember, there’s absolutely nothing wrong with buying a used 7th gen Intel PC and filling that with [insert drive of choice]. An i7-7700T is still more powerful than even the newer Synology units.

So you built your own NAS, then. NAS is just an acronym, “Network Attached Storage”. Not a singular line of products.

That said - I also feel the same way about Synology and the other “all-in-one NAS” brands. Expensive for what they are, which is essentially an incredibly cheap PC with a built in toaster. I built my NAS out of a 2014 Mac Mini (running OMV) and a Sabrent USB-C 4-bay drive dock, and even full of WD Reds, that entire rig is literally half the price of a DS920+. And more powerful.

Why did you embed the link? Just paste the link directly into your comment.

https://www.firesticktricks.com/jailbreak-fire-stick.html

We have a couple Apple TVs. As much as I dislike the walled garden, they are very good for what they are.

No.

I got my 7900XTX for MSRP in 2023 and have no plans on “upgrading” any time soon. The same PC’s 5800X3D is also showing no signs of letting up, and given the tariff bullshit going on right now, I plan on keeping it that way for as long as possible.

My UDM has this capability. I’ve blocked quite a few countries that it logged as trying to get into my network. Great little internet cylinder.

I haven’t experienced this, oddly enough. Many of my compose files have comments, and they’re still visible 🤔

Let us know if you run into more snags! I’m happy to try to help out. I also revised my comment above several times last night and this morning as I was really tired and kept forgetting details 😅

The other thing to note is the “Scan Stacks Folder” option in the drop-down menu. I haven’t really needed to use it as Dockge tends to find my compose files on its own, but it’s worth mentioning.

It’s needed because that’s how Dockge manages the compose files - it needs to know where your compose files live. Dockge normally lives in it’s own directory, /opt/dockge/ (the dev gave a reason for that, but I don’t remember why), so it won’t see anything else until you point it to wherever your compose files are normally located.

The env variable is within the compose file itself - it’s fairly simple.

I think you might be misunderstanding here, Dockge doesn’t really work like that. You don’t import “into” Dockge - it works alongside Docker, and all you need to do is point it to where your compose files are located. Which, like I said, is normally set to /opt/stacks/ - but that’s not set in stone and can be changed to another location via the DOCKGE_STACKS_DIR= env variable within Dockge’s own compose file (located in /opt/dockge/).

For example: Say I create the directory /opt/stacks/docker_container/, drop in my “docker_container” compose.yml file, and fire it up in the terminal with docker compose up -d, all via CLI without touching Dockge at all. Dockge will still automatically see the compose file and the stack status. Or, say I have a previously-established Docker host with all the compose files in a location such as /home/username/docker_stacks/, and I really don’t want to move them - so long as Dockge is configured to point at that directory, and the directory contains a labeled folder for each compose file (just like you would do normally), again, Dockge will automatically see the compose files and stack status. I’ve configured multiple hosts to use Dockge, and it’s really that simple.

Also, something I just remembered - the directory structure for your compose files, wherever it’s located, needs to be all lowercase. Otherwise Dockge won’t see it.

If the compose.yml can be moved to a place where Dockge is configured to look, then yes. Normally it’s configured to look in /opt/stacks/, but that can be changed.