-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.pkgr.yml to enable packaging on packager.io #2
base: master
Are you sure you want to change the base?
Conversation
For the database URL you actually need to define multiple variables, see: https://github.com/Kinto/kinto/blob/master/docker-compose.yml#L12-L18 |
Ideally we wanted to create a /etc/kinto.ini file with the default configuration. |
@Natim ok, what would be the default config? I can put that in a postinstall file |
Ideally we should propose a production ready conf. Having systemd managing a uwsgi daemon. You can have a first version of this configuration file (with most of the production settings as comments) by running |
Oh, I missed this! Thanks for taking the time to do this @crohr. You can generate a default configuration file by running
Let me know if you need any more help on this. |
Any status update on this? I'd really like to have this feature. |
@Natim I can have another look. However, do you know if the kinto.ini file can take environment variables instead of hard-coded values? |
Yes it can 👍 |
Should we update this PR or close it? |
@Natim if you think having native packages still has value, then I'm available to help push this, otherwise I suppose you can close it. Let me know either way :) |
I still think it can be interesting yes. |
This change enables packaging on Packager.io for the major linux distributions (see https://packager.io/gh/pkgr/kinto-heroku/build_runs/3 for an example build).
I tried to test the resulting package, but not sure what's going on after I set a proper DATABASE_URL:
Install the package:
Trying to run the
web
process:Setting a proper
DATABASE_URL
:Then re-running
web
process:Can you tell what's wrong?