Skip to content
This repository was archived by the owner on Feb 12, 2022. It is now read-only.

Commit 3e868ed

Browse files
committed
📚 update docs for Kong 1.0.0
1 parent 2b38f06 commit 3e868ed

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

README.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
Kong as a Heroku app
22
====================
3-
Deploy [Kong 1.0 release candidate 3](https://discuss.konghq.com/t/kong-1-0-rc3-available-for-testing/) clusters to Heroku Common Runtime and Private Spaces using the [Kong buildpack, kong-1.0 branch](https://github.com/heroku/heroku-buildpack-kong/tree/kong-1.0).
3+
Deploy [Kong 1.0.0](https://konghq.com) clusters to Heroku Common Runtime and Private Spaces using the [Kong buildpack, kong-1.0 branch](https://github.com/heroku/heroku-buildpack-kong/tree/kong-1.0).
44

55
**Upgrading from an earlier version?** See [Upgrade Guide](#user-content-upgrade-guide).
66

@@ -141,11 +141,13 @@ See these examples of [Using Terraform with Heroku](https://devcenter.heroku.com
141141

142142
#### The buildpack
143143

144-
[Buildpack v6.0.0](https://github.com/heroku/heroku-buildpack-kong/releases) supports rapid deployments using a
144+
[Buildpack v6.0.0](https://github.com/heroku/heroku-buildpack-kong/releases) supports rapid deployments using a
145145
pre-compiled Kong binary. A pre-existing, customized app may require changes continue functioning, if the app explicitly uses the `/app/.heroku` directory prefix.
146146

147147
[Buildpack v7.0.0-rc\*](https://github.com/heroku/heroku-buildpack-kong/releases) supports Kong 1.0 release candidates. The "rc" releases only support upgrading from Kong 0.14, not earlier versions or other release candidates.
148148

149+
[Buildpack v7.0.0](https://github.com/heroku/heroku-buildpack-kong/releases) supports Kong 1.0.
150+
149151
▶️ See [UPGRADING the buildpack](https://github.com/heroku/heroku-buildpack-kong/blob/master/UPGRADING.md).
150152

151153
#### Kong
@@ -161,7 +163,8 @@ Then, take into account these facts about how this Kong on Heroku app works:
161163
1. [perform the upgrade](https://github.com/Kong/kong/blob/master/UPGRADE.md)
162164
1. allow release process to run
163165
1. finally restart to the original formation size `heroku ps:scale web=$PREVIOUS_SIZE`
164-
* once Kong 1.0 is successfully deployed, execute: `heroku run "kong migrations finish"`
166+
* once Kong 1.0 is successfully deployed, execute: `
167+
heroku run "kong migrations finish --conf /app/config/kong.conf"`
165168

166169
🏥 Please [open an issue](https://github.com/heroku/heroku-kong/issues), if you encounter problems or have feedback about this process.
167170

@@ -398,7 +401,7 @@ heroku info
398401

399402
1. Ensure [requirements](#user-content-requirements) are met
400403
1. Create the Postgres user & databases:
401-
404+
402405
```bash
403406
createuser --pwprompt kong
404407
# set the password "kong"
@@ -414,7 +417,7 @@ heroku info
414417
bin/start
415418
```
416419

417-
* Logs in `/usr/local/var/kong/logs/`
420+
* Logs in `/usr/local/var/kong/logs/`
418421
* Prefix is `/usr/local/var/kong` for commands like:
419422
* `kong health -p /usr/local/var/kong`
420423
* `kong stop -p /usr/local/var/kong`

0 commit comments

Comments
 (0)