Display git version for easier identification

[ronaldtse]

@phuonghuynh can we display git hash at the footer so we know what version is currently deployed?

[maccraymer]

Thanks for suggesting this Ron. I was thinking the same thing - some kind of software version number along with the last revised time stamp of the database. Sent from my iPhone with autocorrect typos On Jun 2, 2020, at 9:09 AM, Ronald Tse <[email protected]> wrote:  @phuonghuynh<https://github.com/phuonghuynh> can we display git hash at the footer so we know what version is currently deployed? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#108>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGURRKLSSGLHZE4TBFCZGUTRUT2XTANCNFSM4NQW2LVQ>.

[phuonghuynh]

@ronaldtse @maccraymer yes, already did

[ronaldtse]

Thanks @phuonghuynh !

[ronaldtse]

@phuonghuynh but the current production still shows this?

(The commit hash is accurately at the latest commit, though, so it's only the date shown that is outdated)

[maccraymer]

The date/time stamp at the bottom every Registry web page was supposed to be the date the database was last updated, not the software version? I thought you were going to add the software revision along with this, not replace it. I think we need to provide a version identifier for both the software and the database. My suggestion is:

Software revision: yyyy-mm-ddThh.mmZ, Database last updated: yyyy-mm-ddThh.mmZ

By the way, does the software have a name? If not, can we give it one in consultation with Florian?

[ronaldtse]

Software revision: yyyy-mm-ddThh.mmZ, Database last updated: yyyy-mm-ddThh.mmZ

Sorry got confused -- this sounds good.

By the way, does the software have a name? If not, can we give it one in consultation with Florian?

Don't think so at the moment. Any suggestions?