diminou

@diminou@lemmy.zip

• ⁨Comment⁩ on ⁨Planning to selfhost images and calendar in addition to HTTP(S)⁩ ⁨⁨15⁩ ⁨hours⁩ ago⁩:

  You could probably go for nextcloud.yourdomain.ddns.org, but I can’t guarantee that since I have no experience with ddns.org.

  There is a lot of cheap registrars, I’ll let you check and select the one you want if you need a second domain.

  Basically docker let you setup multiple (fake) computers inside your computer. For those that want to correct this, I know. But I’m trying to explain the top view here.

  So, your computer (host) is hosting multiple containers, each containers will have there set of available ports. And as stated earlier each container will have an application that may or may not need to expose ports. But since each have their own ports you can have hundreds of containers using the port 80 INSIDE the container, an using 80100 to 80200 OUTSIDE the container (on your host). The only real limit would be the amount of ports available (somewhere along the lines of 65535).

  There. Now go have fun and read up on docker and reverse proxy! Don’t forget to use ssl on your nextcloud instance since it’ll be facing the internet! And… Have fun! :-)

• ⁨Comment⁩ on ⁨Planning to selfhost images and calendar in addition to HTTP(S)⁩ ⁨⁨20⁩ ⁨hours⁩ ago⁩:

  OK you are thinking at it the wrong way : 80 and 443 are the default ports for the web access of any web application.

  You are using docker with the nextcloud aio image. Which mean, you are deploying a docker container which contain the web application.

  What you are doing is using arbitrary ports for the container. This could be 7777. Then, this is redirected to 443 inside the container, to the web application.

  This is why you can actually use any port you want for your container. You are not really switching the port for nextcloud, only for the container.

  This is why I suggested doing 444:443 in the docker-compose.yml file: you are exposing 444 to the container, to 443 inside the container.

  And this is why you can actually use any ports for every web app you are going to host : apache will redirect to the port you want to the container, a’d docker will redirect inside the container to either 80 or 443 (or anything else needed for that web application).

• ⁨Comment⁩ on ⁨Planning to selfhost images and calendar in addition to HTTP(S)⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  In fact 80 and 443 refer to http and https, those are default ports.

  You can in fact use the ports you want for the service you want. I have multiple web services behind the ports 80 and 443, you need one service that is able to get the request at the correct port. This is the role of the reverse proxy.

  Apache can assume that role, you go to anything.yourdomain.com and apache will then redirect “anything” to the correct service (with the internal ip and port). So say you want to put nextcloud at 7777 you can tell docker to expose 7777 and redirect it to 443 on nextcloud.

  The chain is like that in the case : nextcloud.yourdomain.com > apache > nextcloud is at ip:7777 > redirect the request to 7777 > nextcloud homepage is shown

• ⁨Comment⁩ on ⁨Planning to selfhost images and calendar in addition to HTTP(S)⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  OK forget about the ports. Use the docker image of nextcloud, whatever flavor you want.

  In the docker compose you change 80:80 and 443:443 to 81:80 and 444:443.

  Then, you configure your already available apache to redirect nextcloud.yourdomain.com to yourip:444.

  That’s it. You just launched nextcloud with an arbitrary port which is not the default because it suits your needs, a’d configured apache to redirect to that port.