DJ Sundog 74eff5456c 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-11 20:32:16 -04:00
2016-02-20 22:53:20 +01:00
2017-05-23 16:54:44 +02:00
2017-06-23 21:45:14 +00:00
2017-06-23 16:05:04 +02:00
2016-02-20 22:53:20 +01:00
2017-06-23 16:05:04 +02:00
2017-05-23 16:54:44 +02:00
2017-04-15 02:05:41 +02:00
2016-02-25 00:17:01 +01:00
2017-04-06 07:53:48 -04:00
2017-06-22 13:24:00 +02:00
2017-05-12 14:33:54 +02:00
2017-04-17 21:28:31 +02:00
2017-06-27 13:41:03 +02:00
2016-02-20 22:53:20 +01:00
2017-06-30 12:36:10 -04:00
2017-04-10 21:48:30 +02:00

Mastodon Glitch Edition

Now with automated deploys!

Build Status

So here's the deal: we all work on this code, and then it runs on dev.glitch.social and anyone who uses that does so absolutely at their own risk. can you dig it?

Description
No description provided
Readme AGPL-3.0 1.1 GiB
Languages
Ruby 64.4%
JavaScript 17.3%
TypeScript 8.7%
SCSS 4.7%
Haml 4.4%
Other 0.5%