Spyke

Replies

linux

Comment on

*Permanently Deleted*

Personal opinion. If you successfully booted Debian, stick with it. No need to try out a bunch of distros. Debian is well known, well supported, tons of resources AND everything works out of the box with your POS systems. Sold!

Comment on

Please help with distro decision

Nobara has been an absolute pleasure and “works out of the box” experience. Mainly due to having things preinstalled or prompting for installation of gaming dependencies and software up front.

My “get into Linux gaming” distro was Pop. Solid distro tho and having isos depending on your hardware is super helpful and cuts down on a lot of issues you may encounter with other distros. You can’t go wrong either way. If you are looking for a “do it for me/minimal tinkering and installing” go for Nobara. If you are looking to “possibly tinker/install a bit more up front” go for Pop.

Edit: Forgot to mention my specs are somewhat the same as your. i5 with 16gbs of RAM, 1080ti and 1tb ssd. Both Pop and Nobara run smoothly with heavy games like Cyberpunk as an example.

Comment on

NGinx Proxy Manager and Domain Routing to Docker Services on Specific Ports

When you created your containers, did you create a “frontend” and “backend” docker network? Typically I create those two networks (or whatever name you want) and connect all my services (gitlab, Wordpress, etc) to the “backend” network then connect nginx to that same “backend” network (so it can talk to the service containers) but I also add nginx to the “frontend” network (typically of host type).

What this does is it allows you to map docker ports to host ports to that nginx container ONLY and since you have added nginx to the network that can talk to the other containers you don’t have to forward or expose any ports that are not required (3000 for gitlab) to talk from the outside world into your services. Your containers will still talk to each other through native ports but only within that “backend” network (which does not have forwarded/mapped ports).

You would want to setup your proxy hosts exactly like you have them in your post except that in your Forward Hostname you would use the container name (gitlab for example) instead of IP.

So basically it goes like this

Internet > gitlab.domain.com > DNS points to your VPS > Nginx receives requests (frontend network with mapped ports like 443:443 or 80:80) > Nginx checks proxy hosts list > forwards request to gitlab container on port 3000 (because nginx and gitlab are both in the same “backend” network) > Log in to Gitlab > Code until your fingers smoke! > Drink coffee

Hope this help!

Edit: Fix typos

Comment on

Should I learn Docker or Podman?

Honestly, if you have never used containers before I would suggest starting with docker as it has more readily accessible beginner walk through and tutorials. From there, you will have a good idea as to switching to podman is the right move for you or not.

Personally, I started with docker and haven’t moved from there since I don’t see a need (yet). I have dozens of services running on docker. I don’t know how heavy of a lift it would be to learn podman but like I said, I don’t feel the need to do so.

Maybe try out both and see which one you like more?

Comment on

What am I dealing with?

Reply in thread

For the last few days, 100 degrees. Full sun (8am - 6pm). As they were getting established (it’s a new raised bed), I watered daily. Lately I’ve been trying to water every other day depending on how the soil on top looks. I added some compost about a month or so ago. As far as the little bugs, I don’t think I have seen them but I also haven’t been looking.

Comment on

Business Continuity Plan if the worst happen

Honestly, haven’t even though about it. Better make this my weekend project.

Someone mentioned having a static page with instructions (home.example.com/emergency or something similar) not a bad idea at all. Actually this might the route I take too. Thank you for talking about something I didn’t even know I needed!

Comment on

Question about printing times

Something else to check is your infill percentage. Make sure you don’t have it at 100% (unless you absolutely need to build something completely solid). Another thing to check is your print speed. Too low and it will take a decade to print something simple. Too fast and it cause your print to fail. At this point we will all be throwing spaghetti against the wall. Can you share a screenshot of your settings?

linux

Comment on

Friendly reminder

Reply in thread

Ah okay well I appreciate the response anyways. I’m also struggling to figure how to snapshot my /home since I put it in a different partition during install. Timeshift is “unable to see it”.