concourse/hack/keys
Alex Suraci 36db6a583d generalize docker-compose.yml a bit
* rather than generating keys in the 'Dockerfile', which is slow and
  makes the image behave differently from the dev or shipped images,
  just check them in. (obviously do not use these - or any of this
  workflow - in production.)
* same for vault certs, to make vault testing easier.
* move port mappings and '.' mapping to hack/overrides/dev.yml, which is
  now symlinked to docker-compose.override.yml to maintain the previous
  'docker-compose up' dev workflow.

this will make it easier to re-use docker-compose.yml for dev images and
for testing against final images. the aim here is to avoid ha

Signed-off-by: Alex Suraci <suraci.alex@gmail.com>
2021-01-28 17:08:18 -05:00
..
authorized_worker_keys generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00
session_signing_key generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00
setup generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00
tsa_host_key generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00
tsa_host_key.pub generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00
worker_key generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00
worker_key.pub generalize docker-compose.yml a bit 2021-01-28 17:08:18 -05:00