Run Kong API Gateway, Community Edition development setup with docker-compose. Includes Konga as admin webapp.
Originally based on Yuan Cheung's docker-compose-kong, with the following additions:
- Add declarative configuration examples
- Includes securing Kong Admin API
- Use PostgreSQL 9.6 over 9.5, and Alpine Linux based image for smaller size
- Prefer
kong-migration
for initializing the database, rather thansetup.sh
- Prefer Docker's own health checks, over using
wait-for-it.sh
- Remove
bash
from built images, as it is not then needed - Tidy up
docker-compose.yml
, removedlinks
as they are not mandatory here - Remove
start.sh
asdocker-compose restart
is a single command anyway - Add MongoDB for storing Konga users
- Improve healthchecks for checking if database migrations have ran
- Upgrade Kong to 1.0.0rc3, use Alpine Linux based image for smaller size
- Upgrade Kong Dashboard to latest, to support Kong >= 0.13
- though commented out in
docker-compose.yml
as Konga is enough
- though commented out in
docker-compose up
See examples of managing APIs with YAML.
- Proxy: http://localhost:8000
- Proxy w/ SSL: https://localhost:8443
- Admin API: http://localhost:8001
Kong uses PostgreSQL (9.6) with a persistent Docker volume for its credentials.
The following default users are configured in konga/user_seed.js
:
- admin / adminadminadmin
- demo / demodemodemo
After logging in as admin, create a new connection with URL http://kong:8001
.
Konga uses MongoDB (4.1) with a persistent Docker volume for its credentials.