vps/roles/etebase/templates/docker-compose.yaml

services:  
  etebase:
    image: docker.io/victorrds/etebase:alpine
    container_name: etebase
    restart: always
    user: {{ users['etebase'] }}:{{ users['etebase'] }}
    environment:
      SERVER: http
      AUTO_UPDATE: 'true'
    ports:
      - 127.0.0.1:{{ ports['etebase'] }}:3735
    volumes:
      - {{ volumes['etebase_datadir'] }}:/data
      - ./etebase-server.ini:/data/etebase-server.ini
The Great Ansible Update. 2024-02-17 19:01:04 +01:00			`services:`
			`etebase:`
Add docker.io prefix to container image names. 2024-03-02 12:13:30 +01:00			`image: docker.io/victorrds/etebase:alpine`
The Great Ansible Update. 2024-02-17 19:01:04 +01:00			`container_name: etebase`
			`restart: always`
			`user: {{ users['etebase'] }}:{{ users['etebase'] }}`
			`environment:`
			`SERVER: http`
			`AUTO_UPDATE: 'true'`
			`ports:`
Docker: Publish ports to localhost + proxy to ip to reduce lookups. 2024-02-18 22:19:55 +01:00			`- 127.0.0.1:{{ ports['etebase'] }}:3735`
The Great Ansible Update. 2024-02-17 19:01:04 +01:00			`volumes:`
			`- {{ volumes['etebase_datadir'] }}:/data`
Etebase: Add etebase-server.ini template. Some environment variables set in docker compose file (TIME_ZONE, ALLOWED_HOSTS) are used only if the etebase-server.ini file doesn't exist, which can be misleading. If we change these variables after the etebase-server.ini file has been generated, the settings won't be updated in the config file. Templating this file allows changing these settings after the first run. 2024-02-23 12:41:39 +01:00			`- ./etebase-server.ini:/data/etebase-server.ini`