Now you've created (and tested) an awesome Local Library website, you're going to want to install it on a public web server so that it can be accessed by library staff and members over the Internet.
This article provides an overview of how you might go about finding a host to deploy your website, and what you need to do in order to get your site ready for production.
Once your site is finished (or finished "enough" to start public testing) you're going to need to host it somewhere more public and accessible than your personal development computer.
Up to now you've been working in a development environment, using the Django development web server to share your site to the local browser/network, and running your website with (insecure) development settings that expose debug and other private information.
Authentication setup has been changed and some internal modules have changed name, please adjust your If you have some monolingual translations, Weblate now allows to edit template (source) strings as well.
To see them, you need to reload translations, what will either happen automatically on next repository update or you can force it manually: If you have not yet performed upgrade to Django 1.7 and newer, first upgrade to 2.2 following instructions above.
Since version 2.11, there is reduced support for migrating from older not released versions.For the most part, Python aims to be a clean and consistent language that avoids surprises.However, there are a few cases that can be confusing to newcomers.If you are translating monolingual files, it is recommended to rerun quality checks as they might have been wrongly linked to units in previous versions.The migration of database structure to 1.8 might take quite long, it is recommended to put your site offline, while the migration is going on.Theoretically, this behavior is on by default, for performance reasons.