Custom front end for Mastodon
Go to file
2016-08-24 18:51:36 +02:00
app Dockerfile adjustments 2016-08-24 18:51:36 +02:00
bin Upgrade to Rails 2016-08-17 17:58:00 +02:00
config Adding React.js, Redux, revamping dashboard 2016-08-24 17:56:44 +02:00
db Upgrade to Rails 2016-08-17 17:58:00 +02:00
lib Fix subscriptions:clear task, refactor feeds, refactor streamable activites 2016-03-25 02:13:30 +01:00
log Initial commit 2016-02-20 22:53:20 +01:00
public Adding favicon 2016-03-18 12:36:57 +01:00
spec Fixing more configuration issues with ActionCable 2016-08-18 18:39:35 +02:00
vendor/assets Initial commit 2016-02-20 22:53:20 +01:00
.dockerignore Dockerfile adjustments 2016-08-24 18:51:36 +02:00
.env.production.sample Fixing the docker container setup (with assets compilation &co) 2016-03-16 12:57:01 +01:00
.gitignore Adding React.js, Redux, revamping dashboard 2016-08-24 17:56:44 +02:00
.rspec Adding a Mention model, test stubs 2016-02-25 00:17:01 +01:00
.ruby-version Initial commit 2016-02-20 22:53:20 +01:00
.travis.yml Increase note truncation length on account grids, improve FanOutOnWrite a bit, 2016-03-21 08:44:30 +01:00 Initial commit 2016-02-20 22:53:20 +01:00
docker-compose.yml Adding Sidekiq for background processing (firstly just of mailers) 2016-03-25 02:50:48 +01:00
Dockerfile Dockerfile adjustments 2016-08-24 18:51:36 +02:00
Gemfile Adding React.js, Redux, revamping dashboard 2016-08-24 17:56:44 +02:00
Gemfile.lock Adding React.js, Redux, revamping dashboard 2016-08-24 17:56:44 +02:00
LICENSE Adding GNU Public license, adding home timeline, reblog/favourite counters 2016-03-06 17:52:23 +01:00
package.json Adding React.js, Redux, revamping dashboard 2016-08-24 17:56:44 +02:00
Rakefile Initial commit 2016-02-20 22:53:20 +01:00 Linking badges 2016-03-21 09:19:16 +01:00


Build Status Code Climate

Mastodon is a federated microblogging engine. An alternative implementation of the GNU Social project. Based on ActivityStreams, Webfinger, PubsubHubbub and Salmon.

Current status of the project is early development. Documentation &co will be added later


  • GNU Social users can follow Mastodon users
  • Mastodon users can follow GNU Social users
  • Retweets, favourites, mentions, replies work in both directions
  • Public pages for profiles and single statuses
  • Sign up, login, forgotten passwords and changing password
  • Mentions and URLs converted to links in statuses
  • REST API, including home and mention timelines
  • OAuth2 provider system for the API
  • Upload header image for profile page
  • Deleting statuses, deletion propagation


  • LOCAL_DOMAIN should be the domain/hostname of your instance. This is absolutely required as it is used for generating unique IDs for everything federation-related
  • LOCAL_HTTPS set it to true if HTTPS works on your website. This is used to generate canonical URLs, which is also important when generating and parsing federation-related IDs
  • HUB_URL should be the URL of the PubsubHubbub service that your instance is going to use. By default it is the open service of Superfeedr

Consult the example configuration file, .env.production.sample for the full list.


  • PostgreSQL
  • Redis

Running with Docker and Docker-Compose

The project now includes a Dockerfile and a docker-compose.yml. You need to turn .env.production.sample into .env.production with all the variables set before you can:

docker-compose build

And finally

docker-compose up -d

As usual, the first thing you would need to do would be to run migrations:

docker-compose run web rake db:migrate

And since the instance running in the container will be running in production mode, you need to pre-compile assets:

docker-compose run web rake assets:precompile

The container has two volumes, for the assets and for user uploads. The default docker-compose.yml maps them to the repository's public/assets and public/system directories, you may wish to put them somewhere else. Likewise, the PostgreSQL and Redis images have data containers that you may wish to map somewhere where you know how to find them and back them up.


This approach makes updating to the latest version a real breeze.

git pull

To pull down the updates, re-run

docker-compose build

And finally,

docker-compose up -d

Which will re-create the updated containers, leaving databases and data as is. Depending on what files have been updated, you might need to re-run migrations and asset compilation.