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.

54 lines
2.4 KiB

8 years ago
8 years ago
  1. Mastodon
  2. ========
  3. [![Build Status](https://travis-ci.org/Gargron/mastodon.svg?branch=master)](https://travis-ci.org/Gargron/mastodon)
  4. Mastodon is a federated microblogging engine. An alternative implementation of the GNU Social project. Based on ActivityStreams, Webfinger, PubsubHubbub and Salmon.
  5. **Current status of the project is early development. Documentation &co will be added later**
  6. ## Status
  7. - GNU Social users can follow Mastodon users
  8. - Mastodon users can follow GNU Social users
  9. - Retweets, favourites, mentions, replies work in both directions
  10. - Public pages for profiles and single statuses
  11. - Sign up, login, forgotten passwords and changing password
  12. - Mentions and URLs converted to links in statuses
  13. - REST API, including home and mention timelines
  14. - OAuth2 provider system for the API
  15. - Upload header image for profile page
  16. - Deleting statuses, deletion propagation
  17. ## Configuration
  18. - `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
  19. - `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
  20. - `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
  21. Consult the example configuration file, `.env.production.sample` for the full list.
  22. ## Requirements
  23. - PostgreSQL
  24. - Redis
  25. ## Running with Docker and Docker-Compose
  26. 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:
  27. docker-compose build
  28. And finally
  29. docker-compose up
  30. As usual, the first thing you would need to do would be to run migrations:
  31. docker-compose run web rake db:migrate
  32. And since the instance running in the container will be running in production mode, you need to pre-compile assets:
  33. docker-compose run web rake assets:precompile
  34. 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.