|Eugen Rochko d709151781||3 years ago|
|app||3 years ago|
|bin||3 years ago|
|config||3 years ago|
|db||3 years ago|
|lib||3 years ago|
|log||4 years ago|
|public||4 years ago|
|spec||3 years ago|
|vendor/assets||4 years ago|
|.babelrc||3 years ago|
|.dockerignore||3 years ago|
|.env.production.sample||4 years ago|
|.eslintrc||3 years ago|
|.gitignore||3 years ago|
|.rspec||4 years ago|
|.ruby-version||4 years ago|
|.travis.yml||3 years ago|
|Dockerfile||3 years ago|
|Gemfile||3 years ago|
|Gemfile.lock||3 years ago|
|LICENSE||3 years ago|
|README.md||3 years ago|
|Rakefile||4 years ago|
|config.ru||4 years ago|
|docker-compose.yml||4 years ago|
|package.json||3 years ago|
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
LOCAL_DOMAINshould be the domain/hostname of your instance. This is absolutely required as it is used for generating unique IDs for everything federation-related
LOCAL_HTTPSset it to
trueif HTTPS works on your website. This is used to generate canonical URLs, which is also important when generating and parsing federation-related IDs
HUB_URLshould 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.
The project now includes a
Dockerfile and a
docker-compose.yml. You need to turn
.env.production with all the variables set before you can:
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/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.
To pull down the updates, re-run
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.