mastodon/app/views/about/_version.html.haml

.panel
  .panel-header= t 'about.version'
  .panel-body
    - if @instance_presenter.commit_hash == ""
      %strong= version.version_number
    - else
      %strong= version.version_number
      %strong= "#{@instance_presenter.commit_hash}"
Adds version to about/more and API (#2181) * Adds version. * Cleans up code. * Removes standalone endpoint and adds version to instance endpoint. * Addresses feedback from #2181. 2017-04-21 03:30:59 +02:00			`.panel`
			`.panel-header= t 'about.version'`
			`.panel-body`
First lame pass at adding optional git commit hash display on /about/… (#67) * First lame pass at adding optional git commit hash display on /about/more page. Currently, this is implemented by checking for the existence of a file called CURRENT_RELEASE in the home directory of the user running Mastodon. If the file exists, its contents are added. I've modified my update process to include the following before precompiling assets: git log -1 \| head -n 1 \| cut -d " " -f2 > ~/CURRENT_RELEASE That puts the current commit hash into the file ~/CURRENT_RELEASE, but you figured that out because you're a smart cookie. As I am quite sure this is a horrible methodology for implementing this, I look forward to any improvements you have to offer! * Updated to handle instances that share a user - the CURRENT_RELEASE file now lives in the instance's base directory. This also requires modifying the update hook to `git log -1 \| head -n 1 \| cut -d " " -f2 > CURRENT_RELEASE` 2017-07-12 02:32:16 +02:00			`- if @instance_presenter.commit_hash == ""`
			`%strong= version.version_number`
			`- else`
			`%strong= version.version_number`
			`%strong= "#{@instance_presenter.commit_hash}"`