|
|
@@ -67,7 +67,7 @@ Kong's official documentation can be found at [docs.konghq.com](https://docs.kon
|
|
|
|
|
|
# How to use this image
|
|
|
|
|
|
-First, Kong requires a running Cassandra cluster (3.x+) or PostgreSQL instance (9.5+) before it starts. You can either use the official Cassandra/PostgreSQL containers, or use your own.
|
|
|
+First, Kong requires a running Cassandra cluster (3.x+) or PostgreSQL instance (9.6+) before it starts. You can either use the official Cassandra/PostgreSQL containers, or use your own.
|
|
|
|
|
|
## 1. Link Kong to either a Cassandra or PostgreSQL container
|
|
|
|
|
|
@@ -105,12 +105,12 @@ docker run --rm \
|
|
|
-e "KONG_DATABASE=postgres" \
|
|
|
-e "KONG_PG_HOST=kong-database" \
|
|
|
-e "KONG_CASSANDRA_CONTACT_POINTS=kong-database" \
|
|
|
- kong kong migrations up
|
|
|
+ kong kong migrations bootstrap
|
|
|
```
|
|
|
|
|
|
In the above example, both Cassandra and PostgreSQL are configured, but you should update the `KONG_DATABASE` environment variable with either `cassandra` or `postgres`.
|
|
|
|
|
|
-**Note**: migrations should never be run concurrently; only one Kong node should be performing migrations at a time.
|
|
|
+**Note for Kong < 0.15**: with Kong versions below 0.15 (up to 0.14), use the `up` sub-command instead of `bootstrap`. Also note that with Kong < 0.15, migrations should never be run concurrently; only one Kong node should be performing migrations at a time. This limitation is lifted for Kong 0.15, 1.0, and above.
|
|
|
|
|
|
### Start Kong
|
|
|
|