prepare installable debian package

Things to consider:

• CHANGELOG must be available in the source-code (deb package must have a changelog)
• configuration files should be in /etc/smasch/. It should consist at least of: local_settings.py, gunicorn.socket. The files should be symlinked to source files. Config files must have 0600 privileges (database credentials are in plain text)
• smasch sources should be located at /usr/lib/smasch/ (/opt/smasch/ - /opt/ shouldn't be used by packages according to debian/lintian rules)
• log files should go to /var/log/smasch/. There should be smasch.log and gunicorn.log. Consider rotation of log files.
• smasch sources should be owned by user smasch:smasch
• gunicorn service should be created together with the installation. gunicorn service should be run by user smasch:smasch
• the basic installation should maybe depend on the sqllite db (check how difficult it is to use with current migration scripts), however database should be configured by dbconfig-common (https://www.debian.org/doc/manuals/dbconfig-common/ch-develguide.html)
• don't introduce nginx proxy - describe it in the documentation
• statics/media would have to be served by gunicorn - describe in documentation how to do it with nginx

changed milestone to %1.0.0

added enhancement label

changed the description

looks good - two comments:

• for statics/media use whitenoise
• just to include the motivation behind separate user - it is required so that the other system users won't be able to access configuration files which might be confidential

dear @jacek.lebioda, you mentioned that smasch currently requires python 3.6.9. Is there a problem with version 3.7/3.8?

I'm asking because it makes dependency list a bit easier if I could put version >=3.6.9

When I was making an upgrade, I think I couldn't go higher because the version of Django I've upgraded to was not supporting 3.7. Once Django is upgraded, I think it should be ok.

The easiest way to check would be to try to run docker-compose after changing the base image to 3.7.

created merge request !264 (merged) to address this issue

mentioned in merge request !264 (merged)

changed the description

marked the checklist item CHANGELOG must be available in the source-code (deb package must have a changelog) as completed

marked the checklist item smasch sources should be located at /usr/lib/smasch/ (/opt/smasch/ - /opt/ shouldn't be used by packages according to debian/lintian rules) as completed

marked the checklist item smasch sources should be owned by user smasch:smasch as completed

marked the checklist item log files should go to /var/log/smasch/. There should be smasch.log and gunicorn.log. Consider rotation of log files. as completed

marked the checklist item gunicorn service should be created together with the installation. gunicorn service should be run by user smasch:smasch as completed

marked the checklist item configuration files should be in /etc/smasch/. It should consist at least of: local_settings.py, gunicorn.socket. The files should be symlinked to source files. Config files must have 0600 privileges (database credentials are in plain text) as completed

closed with merge request !264 (merged)

mentioned in commit 89b7c4d4