vaultwarden : cleanup container-compose.yml + PostgreSQL healthcheck

This commit is contained in:
Gitouche 2023-08-10 21:40:43 +02:00
parent 3a57c4b9a7
commit dc14578d6f

View file

@ -2,24 +2,14 @@ version: '3'
services: services:
database: database:
container_name: ${db_container_name} container_name: ${db_container_name}
# Don't upgrade PostgreSQL by simply changing the version number
# You need to migrate the Database to the new PostgreSQL version
image: ${database_image}:${database_version} image: ${database_image}:${database_version}
#mem_limit: 256mb # version 2 only
#memswap_limit: 512mb # version 2 only
#read_only: true # not supported in swarm mode please enable along with tmpfs
#tmpfs:
# - /run/postgresql:size=512K
# - /tmp:size=256K
#environment:
# - POSTGRES_USER=vaultwarden
# - POSTGRES_PASSWORD=
# - POSTGRES_DB=vaultwarden
volumes: volumes:
- database:${database_path}:Z - database:${database_path}:Z
networks: healthcheck:
backend: test: ["CMD-SHELL", "pg_isready -U postgres"]
#restart: always interval: 5s
timeout: 5s
retries: 5
app: app:
container_name: ${container_name} container_name: ${container_name}
@ -28,18 +18,9 @@ services:
- data:/data:Z - data:/data:Z
ports: ports:
- "127.0.0.1:8090:80" - "127.0.0.1:8090:80"
networks:
backend:
depends_on: depends_on:
- ${db_container_name} - ${db_container_name}
# Define networks to allow best isolation
networks:
# Internal network for communication with PostgreSQL/MySQL
backend:
# Define named volumes so data stays in place
volumes: volumes:
# Volume for PostgreSQL/MySQL database
database: database:
data: data: