JC1

I work per stack. Each stack can have multiple services/containers. So one db per stack. I usually work with the compose file provided by the app I want to run and they usually provide their database container in those. My persistent data for a stack is in a single folder for every services. For backup, I only have to backup the compose and environment files and also the persistent folder and that’s it. Every stack is independent from each other so it’s easier to move them from a server to another if I want to use more than one server.

I used to use only one db container for all db. It worked well, until I had a data corruption issue. I had to rollback from a backup for all services that used this db. Then I moved to 1 db per stack and it happened again, but this time, only that stack was impacted, so no big deal. Just did a rollback and everything was fine.

I wouldn’t say they are for everyone. Personally, I love them. Once I’ve learned about them, I just saw a better/faster way to use my computer. I use a dynamic tiling window manager, that way I just don’t have to think about placing windows, they are placed automatically in a pattern I want. They also can be quite lightweight.

There are many types of window managers, manual tiling, dynamic tiling, scrolling. I even saw a mouse focused WM at some point. In the dynamic tiling there are even more subdivision with the different layouts offered or the different way workspaces are.

I tried a few on X11 before chosing qtile, then moved to Wayland, tried sway, but was more into hyprland which is arguably the most popular one on Wayland. Now I have Niri on my laptop and Mangowm on my desktop. Mango is by far my favourite now. It combines dynamic tiling and scrolling. There are even plans to add manual tiling too. A jack of all trade.

I have a surface go 3 and a surface pro 7. The first running cachyos, the second running arch. Both do run fine, but the pro 7 isn’t used much anymore. It used to do BSOD on Windows and on linux it just kernel freezes. Still, linux was a much better experience, except for the camera. The main issue with surfaces is the hardware. Highly prone to failure and not really repairable. I love the form factor as I prefer to use a split ergo keyboard, so a laptop keyboard isn’t useful to me, but I wouldn’t buy another as they aren’t good products long term imo.

I often had to go to the registry on Windows and the registry is way less user friendly than modifying files on Linux. When we say that we have to use the terminal for more complicated things on Linux, it’s usually just modifying files that are well commented so you know exactly what you’re doing. If you can read of course which isn’t always a given.

For sure there are scripts and 3rd party apps that can modify the registry, but you can have the same thing on Linux too.

And today with how advanced KDE and Gnome are, the user needs to go less and less in the files. Almost everything I do is in the home folder too. I require root less and less, mainly to install packages.

I think it mainly comes down with what users are used to. People are used to the quirks of Windows, so Linux becomes scary and hard. If it was the other way around, Windows would be considered to be complicated. That’s my take.

By curiosity, since you’re already using Traefik and Pocket ID, what does Tinyauth provide? Traefik can already do forward auth through a plugin. It redirect to picket ID directly

To manage my docker containers I migrated from and to multiple tools. I started directly with Unraid with individual containers. Then I discovered docker compose and stacks. So I migrated to portainer. Splitting the postgres and mariadb databases were the worst thing in this. Then I tried dockge, so migrated from portainer to that. It lacked some portainer functionality, but was fine for a short while.

Finally I discovered Komodo and migrated to that as it’s FOSS. Now I’m only on Komodo, I have no server limit (5 on portainer), had all the functionality of portainer and more. It is my go-to docker manager and the one I recommend to everyone. The only “issue” is that you need to write the name of the stack and click confirm twice if you want to redeploy, restart, stop, destroy. Or you have to click confirm twice after saving when you edit your files. Not much of an issue and it can also protect from accidental clicks. My next step will be to migrate my stacks compose and env files from UI defined to files on the server that I can sync.

I personally like combining both on desktop. Scrolling for web and occasional file browser or terminal, tiling for coding and ricing, tiling for messaging apps, etc. It depends on the need. That’s why I went with MangoWC. I keep niri for my laptop though (where I also don’t want blur anyway).

To use Excel with macros, I don’t even think the web version will cut it. Your only option is to use something like winboat to use excel inside a windows docker container as far as I know.

Immich photos are one of the main thing I backup. I use duplicacy and I backup to backblaze B2 storage. It does incremental backups. Same thing with docker persistent data or other things I consider important.

Why this complicated setup? Komodo handles auto update by itself. It also update the whole stack at once, so no shutdown of the BD while the app stays up. Just have 2 checkboxes to tick.

The less stuff the better, it’s essential in case you have a failure. I only have to redeploy komodo, then all my stacks will be ready to get back online. I even removed watchtower.

I have a surface go 3 and a surface pro 7. I installed Arch on both and also enabled secure boot. Installing Arch works, but wifi on the installation drive doesn’t work. I plug in a usb hub with Ethernet and I’m fine after. Enabling secure boot is harder, but it can work.

No problem qtile was by far my favorite WM when I used X11. Enjoy your setup!

Is this qtile on Wayland or X11? I used to love qtile, but Wayland features weren’t on par with hyprland. If it’s Wayland, how do you like it?