Hi folks,
My Nextcloud server has been complaining about being out of date for a while and I finally figured out I needed to update Debian, not extcloud. I managed that, but nextcloud choked on the update when I went to bring it up to date and I’ve been wanting to do it all over again and hopefully understand the process a little bitter the second time around.
I have a server on the public cloud (think AWS/Azure/Linode/Digital Ocean) with Docker running on it. Is it feasible for me to load up namecheap, lemmy, and pixelfed on the same server in separate docker containers? Anything I should be aware of before trying this?
I worked in the cloud (once again think MS/Amazon/Big Tech), but my role was only partially technical though I have been a GNU-Linux tinkerer since 2005 or so. That is to say, I have no idea what I’m doing, but I can generally read documentation okay.
I believe my previous install was directly to the server via the repos.
There should be no technical reason why not, with an Nginx reverse proxy in front to handle connecting to the docker containers.
Pardon my ignorance here: that’s essentially what maps the container’s port# to the server’s port#, right? Networking is not my strong suit. :D
Yes, that’s how you’d route the hosts incoming traffic (normally to port 443 and redirect 80 to SSL 443) to the ports set for the containers
Docker has built-in port mapping for that (-p in docker run). Nginx does effectively let you do additional port mapping but it’s most commonly used to let you map a subdomain to a port (virtual host) and/or perform SSL termination.
That way you can hit https://service.host.com instead of http://host.com:4829
you could use yunohost to host all of those too
