We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Can packaging improve Django deployments?

Formale Metadaten

Titel
Can packaging improve Django deployments?
Serientitel
Anzahl der Teile
34
Autor
Lizenz
CC-Namensnennung - keine Bearbeitung 4.0 International:
Sie dürfen das Werk in unveränderter Form zu jedem legalen Zweck nutzen, vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
How can packaging Django projects make deployments easier, faster and more reliable? Deployments of Django projects can be a challenging task. Beside the Python source code itself you usually have to handle a lot of other stuff: Installing Python dependencies Shipping JavaScript code and installing it's dependencies Compiling SCSS to CSS Collecting static files Building documentation Compiling translations … And of course you want a deployment approach that is independent of a specific hosting solution. Also you have to think about the scalability of your deployment when the number of servers you operate increases. This usually means that git pull is not the best way to deal with these tasks. So I will discuss different ways to package your Django project like Wheels JavaScript packages Operating system packages Containers Some of these concepts will hopefully help you to make your deployment process easier, faster and more reliable.