Docker-based Concourse deployment
Tool rely on Traefik to expose Web UIs through
*.dev.localhost (see below for more details). All main ports are randomly exposed on Docker host. Use
docker port <container> to get host port numbers.
./manage.sh start script to create and initialize containers.
--pull options can be used respectively to remove pre-existing data/container and update Docker image. A list of services can also be provided but all are started by default.
Note: All created Docker objects are tagged with label
project=concourse to easily identify them.
Start requested services (all by default) and (re-)create and initialized all needed objects.
Note: create Docker custom network if it not already exist, but don't reinitiliazed it when
--clear flag is used.
Print status of container of requested services (all by default).
Try to remove all services (and associated data), then Docker custom network.
Download Concourse CLI (
fly) to provided path (
./fly by default).
Execute the provided vault command (inside Vault container).
Print a summary of available commands.
Custom dedicated network to have embedded DNS to link containers (especially for worker Garden).
Configuration files for Vault server
Data files generated by Vault server
Log files generated by Vault server
Network alias: vault.concourse.local
Vault instance to store Concourse secrets at
Network alias: s3.concourse.local
Network alias: db.concourse.local
PostgreSQL instance which serves as Concourse database to store pipelines, states and logs.
Service: web Network alias: web.concourse.local Ports: 80 Team: main User: admin Password: admin
Service: worker Network alias: worker.concourse.local Ports: none
Concourse Worker instance which will create containers that execute pipeline. Sometimes called agent in other CI/CD tools.