One droplet or two, due to ports?

My current architecture is appWrite, a sveltekit website and a python websocket server. I was trying to deploy the sveltekit and python websocket server as docker containers on the same machine as appWrite. But appWrite needs to be on 80/443 and I think my website needs to be on 80/443 so, does that mean I need a second droplet for my sveltekit website?

Right now the sveltekit website is running as a container on the same droplet but on port 3000.

Learning my way around all of this so any suggestions would be helpful.

so now when I go to my site, I see appWire's login and go to site:3000 I see the website.

In general, you can have multiple services on the same machine and on the same port if they're accessed using a different hostname. You do this by running your services on a non standard port and putting a reverse proxy in front running on 80/443. The reverse proxy receives the request, checks the hostname in the request, and then directs the request to the appropriate service.

I use Nginx Proxy Manager (NPM) because it's a simple GUI interface for Nginx. If you want to try this out, check out https://medium.com/@stnguyen90/how-to-run-appwrite-behind-nginx-19348ed34243

in managing those host names does DigitalOcean have an equivalent service like AWS's Route53?

I'll take a look appreciate the help

I don't think so, but I'm not sure

@Steven I was going through you article above and in the section for "Adding AppWrite to NPM" you say to set the forwarding port to 443. But AppWrite is setup with a different https port (8443 for example). The forwarding port is the internal port I thought? I have a sveltekit app on port 3000 in another docker container and it's forwarding port is 3000.

You would use 443 because the routing is within the docker network rather than from external

so running into this error in the logs "appwrite-traefik could not be resolved (2: Server failure)"

it is the name of the container

Did you put traefik and nginx in the same network?

Here is my proxy manager docker compose:

here is my docker-compose-override for appWrite

here are the networks I see: NETWORK ID NAME DRIVER SCOPE 38ef7bb4acd7 appwrite_gateway bridge local c222c8f99200 bridge bridge local 25ba68b4dc19 host host local 10247f8df87e none null local b6ea3209e71f npmdockernet bridge local

so appwrite is getting its own, so that might be the issue

going to try your docker-compose and overrides from your article verbatim and see

Do docker inspect npmdockernet

I figured it out. appreciate the suggestions

what was the problem?