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`
This commit is contained in:
DJ Sundog 2017-07-11 17:32:16 -07:00 committed by beatrix
parent 60d27b4302
commit 74eff5456c
2 changed files with 15 additions and 1 deletions

View file

@ -29,4 +29,13 @@ class InstancePresenter
def version_number def version_number
Mastodon::Version Mastodon::Version
end end
def commit_hash
current_release_file = Pathname.new('CURRENT_RELEASE').expand_path
if current_release_file.file?
IO.read(current_release_file)
else
""
end
end
end end

View file

@ -1,4 +1,9 @@
.panel .panel
.panel-header= t 'about.version' .panel-header= t 'about.version'
.panel-body .panel-body
%strong= version.version_number - if @instance_presenter.commit_hash == ""
%strong= version.version_number
- else
%strong= version.version_number
%strong= "#{@instance_presenter.commit_hash}"