Feature Request: Ability to run migrations outside of development mode

[slimm609]

The ability to run migrations by specifying the NODE_ENV='migrations' or npm run migrations and have it run the migrations, then exit. This would allow for the migrations to be run and then the container exit.

[jeremyjpj0916]

My workaround for this (depending on your dev environment) was a kubernetes job that is simply "deleted" after 3 mins. So I can run kong in development mode and then the job dies off after the hard limit since i know the db migrations will finish much much sooner than 3 mins. Of course you could call that a hack job but it does suffice for peoples needs.

[schrodingersket]

Would a pull request for this be accepted? I'm also interested in this functionality, and don't at all mind spinning it up.

Thanks in advance!

[pantsel]

@slimm609 , @sashahilton00 , @jeremyjpj0916

this functionality is introduced in Konga 0.11+.

Check https://github.com/pantsel/konga#running-konga

Feel free to reopen the issue if you guys have any probs.