Chris

I use docker to host all kinds of containers - I use unbuntu but that doesn’t matter. I use Let’s encrypt for the certs. Then I use a nginx container to proxy all of that. It’s super easy. Any shell scripts are small and easily understood. I’m not sure why you struggle. I can give you samples that have you up in minutes.

🤣

Pressing caps lock for a single capital letter should be outlawed or be painful or something. That’s just weird.

It’s twoo, it’s twoo

Tex mex at best. But now I’m craving a crisp beef burrito and mexi fries like you can’t imagine.

The comment above stands on its own. Code can be overwhelming - start by going through an existing program and write a comment for every single line - describing exactly what each line does. You’ll pick it up faster than you think.

deleted by creator

Just pass in the name of a json file as a CLI input (or default the name and act on it if present or use it if indicated [e.g. /U == use json.config]).

What process do you use to sign your binaries?

Lazygit. Nice TUI for git.

Hopefully it’ll run Linux with no issues.

I have 4 spinny disks in my NAS. The tile the server is sitting on makes more noise than the drives. I wouldn’t worry about it too much.

I liked having them all in the same file - easier to keep everything in sync. I also had “dependency” links to keep things starting in order.

7 of 9. She’s on the Fediverse…

I used to do this when on Windows too: C was for the OS and apps, D was for user data. The same principle here - separating OS from data is a game changer - and even easier on Linux I think. Makes it so easy to wipe a partition and try something new.