a gnu/social-compatible microblogging server (with optimistic merging)

Eugen 8a58942c80 Fix up recovery codes design a little (#1866) 2 months ago
app 8a58942c80 Fix up recovery codes design a little (#1866) 2 months ago
bin 10ba09f546 Upgrade to Rails 10 months ago
config 363de2dffd Leave out the "Expires" header from S3 uploads (#1886) 2 months ago
db df4ff9a8e1 Add recovery code support for two-factor auth (#1773) 2 months ago
docs f16b9a4928 Fix redirect link on Tuning.md (#1595) 2 months ago
lib fa08b5079d Make the rake mastodon:users:clear task properly clear out unconfirmed users (#1777) 2 months ago
log 9c4856bdb1 Initial commit 1 year ago
public 333e44c3fc Improve emojis - use SVGs where possible 2 months ago
spec 3834e1e69b View spec fix (#1888) 2 months ago
storybook 4d23a85c29 Fix up storybook 3 months ago
streaming 3672a799d4 Dev Tooling fixes (eslint/editorconfig) (#1398) 2 months ago
vendor/assets 9c4856bdb1 Initial commit 1 year ago
.babelrc c4eb63c1d4 Debounce autosuggestions requests 7 months ago
.buildpacks 79765d61f5 Install nodejs before ruby 2 months ago
.codeclimate.yml 8aadb7b0b2 Exclude javascript locale file from dup check (#1677) 2 months ago
.dockerignore f4045ba3d9 Add eslint-plugin-jsx-a11y (#1651) 2 months ago
.editorconfig 3672a799d4 Dev Tooling fixes (eslint/editorconfig) (#1398) 2 months ago
.env.production.sample 7609593e48 Add REDIS_DB env variable to configure Redis database (#1366) 2 months ago
.env.test df4ff9a8e1 Add recovery code support for two-factor auth (#1773) 2 months ago
.env.vagrant 94eccbc5de Add a default LOCAL_DOMAIN=mastodon.dev to .env.vagrant 4 months ago
.eslintignore 3672a799d4 Dev Tooling fixes (eslint/editorconfig) (#1398) 2 months ago
.eslintrc f4045ba3d9 Add eslint-plugin-jsx-a11y (#1651) 2 months ago
.gitignore f4045ba3d9 Add eslint-plugin-jsx-a11y (#1651) 2 months ago
.nvmrc 8482f67caf update Node to 6.x LTS (#1228) 2 months ago
.rspec 71fe24096c Adding a Mention model, test stubs 1 year ago
.rubocop.yml e9737c2235 Fix tests, add applications to eager loading/cache for statuses, fix 5 months ago
.ruby-version 64dbde0dbf Version bumps for ruby and misc gems (#1159) 2 months ago
.slugignore a2adf84858 Updates slugignore. 2 months ago
.travis.yml 8482f67caf update Node to 6.x LTS (#1228) 2 months ago
CONTRIBUTING.md 9e63bf446e Request documentation (#1616) 2 months ago
Capfile 9c88d1b99e Speed up capistrano deployments 4 months ago
Dockerfile f4045ba3d9 Add eslint-plugin-jsx-a11y (#1651) 2 months ago
Gemfile f97272549c Remove unused gem: coffee-rails (#1885) 2 months ago
Gemfile.lock f97272549c Remove unused gem: coffee-rails (#1885) 2 months ago
ISSUE_TEMPLATE.md 904f9266ef Fix typo in ISSUE_TEMPLATE 2 months ago
LICENSE d709151781 Fix #49 - License changed from GPL-2.0 to AGPL-3.0 9 months ago
Procfile 1c351709bc Force UTF8 encoding on generated XML (#1140) 2 months ago
README.md 4445ebdad2 Fix getting started commands out of order (#1737) 2 months ago
Rakefile 9c4856bdb1 Initial commit 1 year ago
Vagrantfile 66ea015a01 Remove current directory from PATH (#1779) 2 months ago
app.json 0dbbc16c69 More SMTP customization (#1372) 2 months ago
config.ru fdc17bea58 Fix rubocop issues, introduce usage of frozen literal to improve performance 7 months ago
docker-compose.yml 0d2910478a Use image too in docker-compose (#1109) 2 months ago
package.json f4045ba3d9 Add eslint-plugin-jsx-a11y (#1651) 2 months ago
scalingo.json 0dbbc16c69 More SMTP customization (#1372) 2 months ago
yarn.lock f4045ba3d9 Add eslint-plugin-jsx-a11y (#1651) 2 months ago



Build Status Code Climate

Mastodon is a free, open-source social network server. A decentralized solution to commercial platforms, it avoids the risks of a single company monopolizing your communication. Anyone can run Mastodon and participate in the social network seamlessly.

An alternative implementation of the GNU social project. Based on ActivityStreams, Webfinger, PubsubHubbub and Salmon.

Click on the screenshot to watch a demo of the UI:


The project focus is 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



  • 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

Consult the example configuration file, .env.production.sample for the full list. Among other things you need to set details for the SMTP server you are going to use.


  • Ruby
  • Node.js
  • PostgreSQL
  • Redis
  • Nginx

Running with Docker and Docker-Compose

The project now includes a Dockerfile and a docker-compose.yml file (which requires at least docker-compose version 1.10.0).

Review the settings in docker-compose.yml. Note that it is not default to store the postgresql database and redis databases in a persistent storage location, so you may need or want to adjust the settings there.

Then, you need to fill in the .env.production file:

cp .env.production.sample .env.production
nano .env.production

Do NOT change the REDIS_* or DB_* settings when running with the default docker configurations.

You will need to fill in, at least: LOCAL_DOMAIN, LOCAL_HTTPS, PAPERCLIP_SECRET, SECRET_KEY_BASE, OTP_SECRET, and the SMTP_* settings. To generate the PAPERCLIP_SECRET, SECRET_KEY_BASE, and OTP_SECRET, you may use:

Before running the first time, you need to build the images:

docker-compose build

docker-compose run --rm web rake secret

Do this once for each of those keys, and copy the result into the .env.production file in the appropriate field.

Then you should run the db:migrate command to create the database, or migrate it from an older release:

docker-compose run --rm web rails db:migrate

Then, you will also need to precompile the assets:

docker-compose run --rm web rails assets:precompile

before you can launch the docker image with:

docker-compose up

If you wish to run this as a daemon process instead of monitoring it on console, use instead:

docker-compose up -d

Then you may login to your new Mastodon instance by browsing to http://localhost:3000/

Following that, make sure that you read the production guide. You are probably going to want to understand how to configure Nginx to make your Mastodon instance available to the rest of the world.

The container has two volumes, for the assets and for user uploads, and optionally two more, for the postgresql and redis databases.

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.

Note: The --rm option for docker-compose will remove the container that is created to run a one-off command after it completes. As data is stored in volumes it is not affected by that container clean-up.


  • rake mastodon:media:clear removes uploads that have not been attached to any status after a while, you would want to run this from a periodic cronjob
  • rake mastodon:push:clear unsubscribes from PuSH notifications for remote users that have no local followers. You may not want to actually do that, to keep a fuller footprint of the fediverse or in case your users will soon re-follow
  • rake mastodon:push:refresh re-subscribes PuSH for expiring remote users, this should be run periodically from a cronjob and quite often as the expiration time depends on the particular hub of the remote user
  • rake mastodon:feeds:clear_all removes all timelines, which forces them to be re-built on the fly next time a user tries to fetch their home/mentions timeline. Only for troubleshooting
  • rake mastodon:feeds:clear removes timelines of users who haven't signed in lately, which allows to save RAM and improve message distribution. This is required to be run periodically so that when they login again the regeneration process will trigger

Running any of these tasks via docker-compose would look like this:

docker-compose run --rm web rake mastodon:media:clear


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

  1. git pull to download updates from the repository
  2. docker-compose build to compile the Docker image out of the changed source files
  3. (optional) docker-compose run --rm web rails db:migrate to perform database migrations. Does nothing if your database is up to date
  4. (optional) docker-compose run --rm web rails assets:precompile to compile new JS and CSS assets
  5. docker-compose up -d to re-create (restart) containers and pick up the changes

Deployment without Docker

Docker is great for quickly trying out software, but it has its drawbacks too. If you prefer to run Mastodon without using Docker, refer to the production guide for examples, configuration and instructions.

Deployment on Scalingo

Deploy on Scalingo

You can view a guide for deployment on Scalingo here.

Deployment on Heroku (experimental)


Mastodon can run on Heroku, but it gets expensive and impractical due to how Heroku prices resource usage. You can view a guide for deployment on Heroku here, but you have been warned.

Development with Vagrant

A quick way to get a development environment up and running is with Vagrant. You will need recent versions of Vagrant and VirtualBox installed.

You can find the guide for setting up a Vagrant development environment here.


You can open issues for bugs you've found or features you think are missing. You can also submit pull requests to this repository. Here are the guidelines for code contributions

IRC channel: #mastodon on irc.freenode.net

Extra credits

  • The Emoji One pack has been used for the emojis
  • The error page image courtesy of Dopatwo

Mastodon error image