• 10 Posts
  • 62 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle
  • ok I checked and you are right, the apache container actually exposes the 11000 port on the host. so i tried following the instructions for “traefik in a docker container on the same machine” and… it still didn’t work (now I was getting a Bad Gateway error)

    at this point I think I’ll just stick with my old setup with docker compose. I was interested in AIO because I thought it could have been an easier to maintain way to host NC (also considering it’s official, while the docker compose method is not) but apparently it’s not meant to be inserted in an already existing setup like mine so I’ll stick with what I currently have.

    it would be nice though if the NC devs also publish a “recommended docker-compose.yaml file” (in a similar way of what Immich does) so that more advanced users still can have an easy way to set everything up without having to look for the correct containers and settings required all over the internet


  • thank you! so, wanting to follow your tip and exposing the 11000 port from the apache container to the host (in order to have a setup that is valid even if I move the service to another machine), how should I do that? because the apache container is also created by AIO’s mastercontainer and so I don’t have a place where to specify its port mapping (while usually I would do it adding 11000:11000 to the ports section of the docker compose)…


  • Thank you! Idk how but I didn’t noticed the paragraph in the docs saying that labels condition is not supported. I’ll try with the file config and see if this way I can make it work. The only thing I’m still missing is the IP of the Apache container: shouldn’t it be an IP on the traefik_net network where also the traefik container runs? And if so how can I specify to the mastercontainer to create the Apache container on that network with a specific IP address?











  • Thank you, but the problem is that is howdy installation (that gets automatically executed after I run sudo apt install howdy that tries to run “old fashioned” pip commands. So I should either find a way to tweak Howdy install (like building it from source after changing something maybe?) or disable this system security feature temporarily, install howdy and re-enable it immediately after


  • Nope I didn’t, but the problem doesn’t seem to be the Python version, but instead the fact that now Python is “externally managed” and therefore I cannot install packages using pip install packagename as it used to be.

    I know that this is done for security reasons and that the good practice would be using pipx or conda, but the problem is that howdy istallation still tries to use the “old approach”






  • Then I would suggest you to take a look at Reverse Proxies, which are programs that let you publicly expose different services hosted on the same computer under different (sub)domains.

    The easiest to start with (and also probably the one that better fits your needs) afaik is NGINX Proxy Manager, which can be set up really easily using docker, and you can find plenty of tutorials online (here is one I watched when I was starting to look into docker and selfhosting, it’s a bit old but should still be valid).

    If after having set up that you will to thinker around it a little bit and dive a bit deeper, there’s also Traefik which is pretty cool and also has a lot of materials to learn online.

    I don’t remember if the video I linked mention it or not, but to use a reverse proxy to expose your services on the web you will first need to set up a dynamic dns (probably the easiest way is to use Cloudflare) or to ask your ISP for a static IP, then go into your routers settings and find the Port Forwarding section where you should tell your routers to send all the incoming traffic from ports 80 (HTTP) and 443 (HTTPS) to the local IP of your server. And then you should be ready to use spin up Nginx Proxy Manager or Traefik on your server.

    (idk if I was clear or not but I swear it’s easier that how it seems ahah)




  • Long time Fedora user here. I’ve used Manjaro for a few months before Fedora and I’ve switched to PopOS! a few months ago because it was better supported from my laptop manufacturer…

    I’ve to admin I was a bit skeptical about switching to a Debian based distro, because I’m someone who likes to follow the latest news in the field and gets exited to try the latest stuff. But then I did and gosh if it’s a smoother experience compared to Fedora! (which itself was a notable smoother experience compared to Manjaro). I’m not saying that Fedora experience was bad, I still think is one (if not the) best compromise between usability and freshness, but I’d say that with Pop I’ve had even less troubles than with windows! The price of that? Being stuck with Gnome 42 after having tried the goodies of newer ones :/

    TL;DR: If you think you can live without the latest magic from the linux community, to then I’d reccommend you Pop. Otherwise Manjaro is a good distro and from what I can remember NVIDIA drivers works almost out-of-the-box but be ready for some frequent minor troubleshooting sessions