Open silenius opened 5 months ago
Thanks @silenius, indeed I wonder for a long time is this approach is sane (ideally, even having the git repository at the deployed location shouldn't be a requirement, I think). I'll look for another approach, the good thing about this one was that it worked everywhere and was easy, but something like running that command at release time and storing its output in a text file might be better!
In
dashboard/templates/dashboard/_footer.html
the version is displayed. It uses:from
dashboard/utils.py
under the hood.In our deployment only some directories are owned and/or writable by the user (for security reasons) and git describe fails:
Another potential issue is that
subprocess.check_output
forks a new process which could be an issue if many clients are hitting the frontpage at the same time