Documentation: Usage with domain, nginx reverse proxy

[TheNomad11]

In class, we cannot use localhost:3000 but need a domain. I would be happy if we could have some documentation about the correct setup in both the docker-compose file and the nginx reverse proxy. I am a bit confused about how to deal with the websocket, for example what is the - SOCKET_URL= and the same in the env-file.

Anyway thanks a lot for the clone, many people have been asking for a Kahoot clone, there have been some but none of them have been convincing so I kept using (and paying for) Kahoot

[TheNomad11]

According to AI ws needs a separate domain, so docker compose:

services:
  rahoot:
    image: ralex91/rahoot:latest
    ports:
      - "127.0.0.1:3500:3000"
      - "127.0.0.1:3501:3001"
    volumes:
      - ./config:/app/config
    environment:
      - WEB_ORIGIN=https://rahoot.example.com
      - SOCKET_URL=https://ws-rahoot.example.com

and nginx:

map $http_upgrade $connection_upgrade {
  default upgrade;
  ''      close;
}

server {
  listen 80;
  server_name rahoot.example.com;

  location / {
    proxy_pass http://127.0.0.1:3500;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
  }
}

server {
  listen 80;
  server_name ws-rahoot.example.com;

  location / {
    proxy_pass http://127.0.0.1:3501;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_set_header Host $host;
    proxy_read_timeout 86400;
  }
}

In my tests this set up is working fine, of course we have to get a letsencrypt certicate as well and change http to https

[Ralex91]

Hi,

In the future version, this configuration will be much simpler.

The Docker image will manage everything internally (including Nginx), so you won’t need to configure a reverse proxy or deal with WebSocket settings manually.

Most importantly:

• You will only need to expose one single port.
• Previously, two ports were required (HTTP + WebSocket).
• In the new version, everything will go through the same internal server and the same port.

So there will be no more SOCKET_URL confusion, no extra proxy setup, and no special configuration needed. Just run the container, expose one port, and connect your domain.

[TheNomad11]

Great, thanks, sounds good, but I hope it is still possible to run it with reverse proxy (nginx on the host), as I have several apps running on docker

[Ralex91]

... as I have several apps running on docker

Yes, that’s totally possible.

The app only uses a single port, so you can easily run it behind your existing Nginx reverse proxy on the host, even with multiple Docker apps.

Just proxy it like your other services, no special configuration needed.

If you're using Nginx, just make sure to enable WebSocket support in your reverse proxy configuration (Upgrade and Connection headers).