packetcat / mastible

An Ansible playbook to install Mastodon

ARCHIVED

THIS REPOSITORY WAS MOVED.

THE NEW REPOSITORY URL IS: https://git.packetcat.ca/packetcat/mastible

mastible

An Ansible playbook to install Mastodon

Requirements

• Latest stable version of Ansible
• Server(s) running Ubuntu 16.04/18.04/20.04 LTS for hosting Mastodon

Testing status

Mastible was tested on 20/08/2020 with Ansible 2.9.12 running against a Ubuntu 20.04 server.

Instructions for running this playbook (first time install)

• Copy group_vars/all.sample to group_vars/all and edit it to specify the database name you wish to use with Mastodon. LOCAL_DOMAIN value is mandatory, it is your instance domain/sub-domain. The PostgreSQL database role will drop this database in preparation for Mastodon's database setup so make sure this is not a database you are currently using
• Copy roles/mastodon-config/templates/.env.production.sample to roles/mastodon-config/templates/.env.production, edit with all relevant details.
• Make a hosts file that looks like this:

[mastodon]
dev.example.social

• Run the playbook with ansible-playbook -i hosts --extra-vars='install=true' site.yml

Instructions for using this playbook to update an existing instance

• Update version number in roles/mastodon-app/tasks/main.yml
• Run the playbook with ansible-playbook -i hosts site.yml (Note the lack of the install variable which is needed for installation related tasks)

mastible's Issues

Allow to be run on existing install

I haven't submitted a PR for this yet (thought I'd probably done enough!) but wondered what you thought about changes so that you could rerun this playbook on an existing install and not have it e.g. wipe the database. This would make it much easier to update mastodon as you could update the version number here, rerun and it would update dependencies, precompile assets and the other needed stuff.

Here's the commit I've done, on top of my other changes, which I have used successfully to upgrade to v2.4.4: dracos@allow-rerunning – it moves the install bits (secret generation, db wipe/reload, gets first LE cert) to separate tasks and only calls them if you run ansible-playbook with --extra-vars='install=true' (there might be a nicer way of doing that, I'm no ansible expert).