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 ef2b50c9ac Deleting statuses from UI 7 years ago
app Deleting statuses from UI 7 years ago
bin Upgrade to Rails 7 years ago
config Adding landing page 7 years ago
db Replace logo, fix #57 - delete/unreblog/unfavourite API, fix #45 - app 7 years ago
lib Upgrade to PubSubHubbub 0.4 (removing verify_token) 7 years ago
log Initial commit 8 years ago
public Fix #56 - Add default avatar 7 years ago
spec Fix tests 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
.rubocop.yml Improve code style 7 years ago
.ruby-version Initial commit 8 years ago
.travis.yml Trying to fix travis builds 7 years ago
Dockerfile Fix typo in dockerfile 7 years ago
Gemfile Improve partial rendering and Haml performance (Haml->Hamlit) 7 years ago
Gemfile.lock Adding landing page 7 years ago
LICENSE Fix #49 - License changed from GPL-2.0 to AGPL-3.0 7 years ago Add screenshot to readme 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 landing page 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. Alternatively, you can donate to this BTC address: 17j2g7vpgHhLuXhN4bueZFCvdxxieyRVWd

Current status of the project is early development



  • Fully interoperable with GNU social and any OStatus platform
    Whatever implements Atom feeds, ActivityStreams, Salmon, PubSubHubbub and Webfinger is part of the network
  • Real-time timeline updates
    See the updates of people you're following appear in real-time in the UI via WebSockets
  • Federated thread resolving
    If someone you follow replies to a user unknown to the server, the server fetches the full thread so you can view it without leaving the UI
  • Media attachments like images and WebM
    Upload and view images and WebM videos attached to the updates
  • OAuth2 and a straightforward REST API
    Mastodon acts as an OAuth2 provider so 3rd party apps can use the API, which is RESTful and simple
  • Background processing for long-running tasks
    Mastodon tries to be as fast and responsive as possible, so all long-running tasks that can be delegated to background processing, are
  • Deployable via Docker
    You don't need to mess with dependencies and configuration if you want to try Mastodon, if you have Docker and Docker Compose the deployment is extremely easy


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