Requiring sudo to update ncharts on production is not practical. The django fixtures database needs to be readable and writable by the apache user. It also has to be updated by non-apache users to add new fixtures and to clear out expired sessions. This jira issue is an example of the problems:
Erik suggests a non-sudo approach here:
We should try and see if that is a more practical and secure approach to deploying production updates. Given that the git repository would be group writable, then that opens the door to git-based deployments, as in #2.
Requiring sudo to update ncharts on production is not practical. The django fixtures database needs to be readable and writable by the apache user. It also has to be updated by non-apache users to add new fixtures and to clear out expired sessions. This jira issue is an example of the problems:
Erik suggests a non-sudo approach here:
We should try and see if that is a more practical and secure approach to deploying production updates. Given that the git repository would be group writable, then that opens the door to git-based deployments, as in #2.