Another approach is to use git commit IDs and/or git tags to track
releases, then display that data (and commit date) in a template, only to
superusers or some group. I did a little blog post about this recently:
http://blog.birdhouse.org/2016/04/22/django_git_template_tag/
./s
--
You receive
You can put the version for your project in:
my_project/my_project/__init__.py (same folder as settings.py)
like this:
__version__ = '1.0.27'
Then your project acts as a python module, and you can refer to the version
number, for instance in your settings.py, as:
GRAPPELLI_ADMIN_TITLE = 'My Pr
I will look it at night.
Thanks
On 3 May 2016 at 11:36, Mike Dewhirst wrote:
> On 3/05/2016 7:21 PM, Martin Torre Castro wrote:
>
>> I'm making a Django project consisting of several apps and I want to use
>> a version number for the whole project, which would be useful for
>> tracking the stat
On 3/05/2016 7:21 PM, Martin Torre Castro wrote:
I'm making a Django project consisting of several apps and I want to use
a version number for the whole project, which would be useful for
tracking the status of the project between each time it comes to production.
I've read and googled and I've
I'm making a Django project consisting of several apps and I want to use a
version number for the whole project, which would be useful for tracking
the status of the project between each time it comes to production.
I've read and googled and I've found how to put a version number for each
dj
5 matches
Mail list logo