2👍
I don’t think I’ve ever needed to do this, but the two obvious choices would be either the settings file, as you state, or alternatively the __init__.py
in the main project app.
1👍
You don’t need it to relate to django, you can tag a commit in your source control to provide a marker of a particular version (as well as a separate branch for releases).
From the docs for git tagging
Git has the ability to tag specific points in history as being important. Typically people use this functionality to mark release points (v1.0, and so on).
You could use the same versioning number system as google if you so wish which relates to
year.month.day.optional_revision # i.e 2016.05.03 for today
Doing this would make it easier to track back to previous versions since it won’t be overwritten in source code by newer version numbers.
- [Django]-RabbitMQ keeps connections running for a long time
- [Django]-Showing a total of items created in a Django model
- [Django]-What's the difference between OneToOne and Subclassing a model in Django
- [Django]-NoReverseMatch with {% url … %} and keyword args