authelia/internal/suites/Postgres/docker-compose.yml

version: '3'
services:
  authelia-backend:
    volumes:
      - './Postgres/configuration.yml:/config/configuration.yml:ro'
      - './Postgres/users.yml:/config/users.yml'
      - './common/ssl:/config/ssl:ro'
Add Traefik2 suite and refactor Traefik suite (#562) * Update Traefik 1.x to v1.7.20 for integration tests * Add suite for Traefik 2.x * Refactor Traefik2 suite to utilise Docker labels * Move Traefik2 middleware definition to a file based provider * Expose Traefik2 dashboard The API/Dashboard can be reached at https://traefik.example.com:8080/ * Move Traefik frontend/backend definitions to Docker labels * Move Traefik2 router/service definitions to Docker labels * Normalise all Traefik configuration via labels and commands When the the middleware issue with Traefik 2.x (#476) is resolved this means all Traefik related configuration can be self-contained within the respective docker-compose.yml files. * Define ports for Authelia frontend/backend services * Adjust Traefik2 suite to new dev workflow * Normalise all Traefik2 middlewares via labels * Fix typo in middleware and comment labels specifying Traefik version 2020-01-19 10:06:37 +00:00			`version: '3'`
Rewrite and fix remaining suites in Go. 2019-11-24 20:27:59 +00:00			`services:`
			`authelia-backend:`
			`volumes:`
[FEATURE] Docker simplification and configuration generation (#1113) * [FEATURE] Docker simplification and configuration generation The Authelia binary now will attempt to generate configuration based on the latest template assuming that the config location specified on startup does not exist. If a file based backend is selected and the backend cannot be found similarly it will generate a `user_database.yml` based a template. This will allow more seamless bootstrapping of an environment no matter the deployment method. We have also squashed the Docker volume requirement down to just `/config` thus removing the requirement for `/var/lib/authelia` this is primarily in attempts to simplify the Docker deployment. Users with the old volume mappings have two options: 1. Change their mappings to conform to `/config` 2. Change the container entrypoint from `authelia --config /config/configuration.yml` to their old mapping * Adjust paths relative to `/etc/authelia` and simplify to single volume for compose * Add generation for file backend based user database * Refactor Docker volumes and paths to /config * Refactor Docker WORKDIR to /app * Fix integration tests * Update BREAKING.md for v4.20.0 * Run go mod tidy * Fix log_file_path in miscellaneous.md docs * Generate config and userdb with 0600 permissions * Fix log_file_path in config.template.yml 2020-06-17 06:25:35 +00:00			`- './Postgres/configuration.yml:/config/configuration.yml:ro'`
			`- './Postgres/users.yml:/config/users.yml'`
			`- './common/ssl:/config/ssl:ro'`