Skip to content
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.

Runtime configuration management #40

Closed
lmorchard opened this issue May 13, 2014 · 0 comments
Closed

Runtime configuration management #40

lmorchard opened this issue May 13, 2014 · 0 comments

Comments

@lmorchard
Copy link
Contributor

Currently, the configuration for Kumascript as deployed in Kuma happens in a kumascript_settings_local.json file that is editable only by IT. This works fine for settings that are infrastructure related (ie. the IP to a memcache server), but not so much for tuning settings (ie. the timeout duration before terminating a hung worker process).

On the Kuma side of things, we have django-constance that lets us alter some runtime settings for the site that does not require attention from IT folks. It would be nice if KumaScript had some settings that could be altered in this way.

@Elchi3 Elchi3 closed this as completed May 23, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants