Introducing versioning
Today, we release version 1.0 of the Helfertool. This does not mean anything special, it is just the first version with a version number.
The new versioning schema is described in the documentation.
Today, we release version 1.0 of the Helfertool. This does not mean anything special, it is just the first version with a version number.
The new versioning schema is described in the documentation.
Deploying a Django application is not always totally easy, especially with dependencies
like Celery and LaTeX.
Therefore, the new and recommended way to deploy the Helfertool is Docker together
with a Debian package called helfertoolctl
that provides things like a systemd service
file.
Together with the Docker container, some more changes were done:
src
directory. Unfortunately, this makes updates of old Helfertool installations more complicated but it was necessary.The installation instructions were updated in order to describe the new setup. It is recommended to migrate existing installations to Docker, the database of course stays the same.
Here are some hints how to move over to Docker:
uwsgi
service.helfertoolctl
. Reuse the already existing database./srv/helfertool/media
.We hope that your migration works smoothly, otherwise please open Github issues for the Helfertool, helfertoolctl or the documentation.
The Helfertool repository now (again) contains all JS and CSS dependencies. This means that npm and bower are no dependency anymore, this should make deployment easier and save around 50MB of disk space.
This means that the node_modules
and helfertool/components
directories
can be removed.
It is recommended to run python manage.py collectstatic --clear
to
remove the old files from the static files directory that is served by
the web server.