How to handle multiple worlds?

[IxsharpxI]

How is it recommended to handle multiple worlds? Could you decide between them or is recommended to run one world per container?

[lloesche]

Whatever you define in WORLD_NAME is what the server will load. The world name corresponds directly to a set of .db/.fwl files in /config/worlds/. E.g. WORLD_NAME=Dedicated will load /config/worlds/Dedicated.db.
There is no artificial limit to the number of worlds you can create.
Whenever you start the container with a new WORLD_NAME the server will generate a set of new world files. Likewise if you have an existing world on your Windows/Linux Desktop you can copy the two files to the /config/worlds/ directory, specify the name in WORLD_NAME without the file extension and load them into the server this way.

[AymanHamdoun]

However, if you do not want to get a domain you can follow the first 2 steps above and disregard all the nginx related stuff and conntect to the server IP : mapped ports

• server:3001 for valheim1
• server:3004 for valheim2

Just make sure that the mapped ports are unblocked from your firewall, you can do so by

ufw allow 3001
ufw allow 3004

(with the subdomain approach only port 2456 needed to be unblocked because ports 3001 & 3004 were accessed internally)

[al13nus]

How to configure this behind Traefik? Any ideas?

[dschof41]

@AymanHamdoun are you using docker-compose to do that? Could you share the yaml that let's you map 3001 > 2456?

[wcdanh2]

Do not use docker's port remapping for the server ports! (if you want your server to appear in the server list.)

When the server tries to publish itself in the server list, if it does not know the actual ports used externally then it will not report correctly. This will result in your server never appearing in the server list, as well as your server never correctly displaying status if you add it to your favorites by its ip/domain.

Instead you should use the SERVER_PORT environment variable and map the port you choose (+1 for the query port) straight through in your docker-compose or docker run args.

[dschof41]

@wcdanh2 in this case I don't care about the server list stuff, but thank you for pointing out the SERVER_PORT method!

here's the yml that's working for me on my old ubuntu 16.04 server. The folder structure here isn't optimal but it fine for now.

version: "2"

services: 
  val1: 
    image: ghcr.io/lloesche/valheim-server
    cap_add:
      - sys_nice
    volumes: 
      - $HOME/valheim-server/config:/config
      - $HOME/valheim-server/data:/opt/valheim
    ports: 
      - "2456-2457:2456-2457/udp"
      - "9001:9001/tcp"
    env_file:
      - $HOME/valheim-server/valheim.env
    restart: always
  val2:
    image: ghcr.io/lloesche/valheim-server
    cap_add:
      - sys_nice
    volumes:
      - $HOME/valheim-server/val2-server/config:/config
      - $HOME/valheim-server/val2-server/data:/opt/valheim
    ports:
      - "3456-3457:2456-2457/udp"
      - "9002:9001/tcp"
    env_file:
      - $HOME/valheim-server/val2-server/v2.env
    restart: always