README.md 2.78 KB
Newer Older
1 2 3
Mastodon
========

4 5
[![Build Status](https://travis-ci.org/Gargron/mastodon.svg?branch=master)](https://travis-ci.org/Gargron/mastodon)

6 7
Mastodon is a federated microblogging engine. An alternative implementation of the GNU Social project. Based on ActivityStreams, Webfinger, PubsubHubbub and Salmon.

8
**Current status of the project is early development. Documentation &co will be added later**
9

Eugen Rochko's avatar
Eugen Rochko committed
10
## Status
11

Eugen Rochko's avatar
Eugen Rochko committed
12 13 14 15 16
- 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
17
- Mentions and URLs converted to links in statuses
18 19
- REST API, including home and mention timelines
- OAuth2 provider system for the API
20
- Upload header image for profile page
21
- Deleting statuses, deletion propagation
Eugen Rochko's avatar
Eugen Rochko committed
22

23 24 25 26 27
## Configuration

- `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
28

Eugen Rochko's avatar
Eugen Rochko committed
29 30
Consult the example configuration file, `.env.production.sample` for the full list.

31 32 33 34
## Requirements

- PostgreSQL
- Redis
35 36 37

## Running with Docker and Docker-Compose

Eugen Rochko's avatar
Eugen Rochko committed
38
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:
39 40 41 42 43

    docker-compose build

And finally

44
    docker-compose up -d
45 46 47 48

As usual, the first thing you would need to do would be to run migrations:

    docker-compose run web rake db:migrate
49 50 51 52 53 54

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.
55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70

### Updating

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.