You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Eugen Rochko 18d21f1a39 Update doorkeeper dependency and replace libav with backported ffmpeg in docker 7 years ago
app Adding webm playback to UI 7 years ago
bin Upgrade to Rails 7 years ago
config Adding media controller, 1 webm/compose form allowed, previews generated 7 years ago
db Add API to upload media attachments 7 years ago
lib Improve rake tasks 7 years ago
log Initial commit 8 years ago
public Adding favicon 8 years ago
spec Test case for new api endpoint 7 years ago
vendor/assets Initial commit 8 years ago
.babelrc Reblogs fixed 7 years ago
.dockerignore Dockerfile adjustments 7 years ago
.env.production.sample Fixing the docker container setup (with assets compilation &co) 8 years ago
.eslintrc Reblogs fixed 7 years ago
.gitignore Adding React.js, Redux, revamping dashboard 7 years ago
.rspec Adding a Mention model, test stubs 8 years ago
.ruby-version Initial commit 8 years ago
.travis.yml Trying to fix travis builds 7 years ago
Dockerfile Update doorkeeper dependency and replace libav with backported ffmpeg in docker 7 years ago
Gemfile Fixing image upload limits, allowing webm, merge/unmerge events trigger 7 years ago
Gemfile.lock Update doorkeeper dependency and replace libav with backported ffmpeg in docker 7 years ago
LICENSE Adding GNU Public license, adding home timeline, reblog/favourite counters 8 years ago Update 7 years ago
Rakefile Initial commit 8 years ago Initial commit 8 years ago
docker-compose.yml Adding Sidekiq for background processing (firstly just of mailers) 8 years ago
package.json Adding a notification stack for error messages 7 years ago


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.

Focus of the project on a clean REST API and a good user interface. Ruby on Rails is used for the back-end, while React.js and Redux are used for the dynamic front-end. A static front-end for public resources (profiles and statuses) is also provided.

If you would like, you can support the development of this project on Patreon.

Current status of the project is early development



  • 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
  • Real-time timelines via Websockets


  • 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.