For debugging traefik/traefik#2576
Includes 2 docker-compose
files: one outdated (Concourse 3.9.0, Traefik 1.5.4), the other updated (Concourse 3.14.0, Traefik 1.6.4). Both appear to work fine and not exhibit the "text/event-stream" network request problem where logs can't be displayed.
# Copy files into a directory.
# For this demo, we'll assume `contraef`.
# This directory name affects the access URL because docker-compose creates
# the stack with this name. You can change it, but watch for reoccurrences.
mkdir contraef
cd contraef
# Copy files from gist into directory:
# docker-compose-updated.yml
# docker-compose-outdated.yml
# pipeline.yml
# traefik.toml
# Bring stack online: choose either -outdated or -updated
docker-compose -f docker-compose-updated.yml up -d
# docker-compose -f docker-compose-outdated.yml up -d
# Ensure this prints out the Concourse landing page HTML
# NOTE THE DIRECTORY NAME HERE (contraef)
curl --header 'Host: concourse.contraef.docker.localhost' 'http://localhost:80/'
# Set local target.
# This target will NOT use Traefik for communication.
fly --target local login --concourse-url http://127.0.0.1:8090
# Ensure fly CLI has right version
fly -t local sync
# Check to see if worker is active
fly -t local workers
# Load new pipeline
fly -t local set-pipeline -p test -c pipeline.yml
# Activate pipe
fly -t local unpause-pipeline -p test
# Run dummy job
fly -t local trigger-job -j test/test-event-stream
# Visit in browser, log in:
chrome http://concourse.contraef.docker.localhost/