Installing a Mastodon Community on Ubuntu Focal Fossa
Mastodon is an open-source, self-hosted, social media and social networking service. It allows you to host your own Instances which may have their own code of conduct, terms of service and moderation policies. There is no central server and Mastodon Instances are connected as a federated social network, allowing users from different Instances to interact with each other. The platform provides privacy features allowing users to adjust the privacy settings of each of their posts.
As there is no central server, you can choose whether to join or leave an instance according to its policy without actually leaving Mastodon Social Network. Mastodon is a part of Fediverse, allowing users to interact with users on other platforms that support the same protocol for example: PeerTube, Friendica and GNU Social.
Mastodon provides the possibility of using S3 compatible Object Storage to store media content uploaded to Instances, making it flexible and scalable.
You may need certain IAM permissions to carry out some actions described on this page. This means:
- you are the Owner of the Scaleway Organization in which the actions will be carried out, or
- you are an IAM user of the Organization, with a policy granting you the necessary permission sets
- You have an account and are logged into the Scaleway console
- You have configured your SSH key
- You have created an Instance that runs Ubuntu Focal Fossa
- You have a domain name or subdomain pointing to the instance
- You have enabled the SMTP ports to send out email notifications
- Connect to your instance via SSH.
- Update the APT packet cache and the software already installed on the instance.
apt update && apt upgrade -y
curlon the system and add an external repository for the required version of Node.js. Install it by running the following commands:Mastodon uses the Yarn package manager.apt install curl -ycurl -sL https://deb.nodesource.com/setup_12.x | bash -
- Install the repository for the required version of Yarn by running the following commands:
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
- Update the system and install Yarn.
apt-get update && apt-get install -y yarn
- Install the following packages, which Mastodon depends on:
- Imagemagick for image related operations
- FFmpeg for conversion of GIFs to MP4s
- Protobuf with
protobuf-compiler, used for language detection
- Nginx as frontend web server
- Redis for its in-memory data structure store
- PostgreSQL is used as SQL database for Mastodon
- Node.js is used for Mastodon’s streaming API
- Yarn is a Node.js package manager
- Certbot is a tool to manage TLS certificated issued by the Let’s Encrypt nonprofit “Certificate Authority” (CA)
g++. These packages are required for the compilation of Ruby using ruby-build.
apt install -y imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git-core g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libgdbm6 libgdbm-dev nginx redis-server redis-tools postgresql postgresql-contrib certbot python3-certbot-nginx yarn libidn11-dev libicu-dev libjemalloc-dev
We are going to use
rbenv to manage Ruby versions. The application must be installed for a single Linux user, therefore, first we must create a user under which Mastodon will run.
7. Run the following command. The
--disabled-login flag disables direct login to the user account for increased security.
adduser --disabled-login mastodon
- Log into the
mastodonuser account and change to the home directory.su mastodoncd
- Set up rbenv and ruby-build:
git clone https://github.com/rbenv/rbenv.git ~/.rbenvcd ~/.rbenv && src/configure && make -C srcecho 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrcecho 'eval "$(rbenv init -)"' >> ~/.bashrc# Restart the users shellexec bash# Check if rbenv is correctly installedtype rbenv# Install ruby-build as a rbenv plugingit clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build
- Install and enable the version of Ruby that is used by Mastodon.
RUBY_CONFIGURE_OPTS=--with-jemalloc rbenv install 2.6.6rbenv global 2.6.6:
This step may take up to several minutes to complete.
- Run the following command to install
bundler:gem install bundler --no-document
- Switch back into the root account by typing
Mastodon requires access to a postgreSQL database to store its configuration and user data.
- Change into the
postgresuser account, run
psqland create a database:sudo -u postgres psql
- Create the database user for Mastodon and exit:
CREATE USER mastodon CREATEDB;\q
- Switch into the
mastodonuser account:su - mastodon
- Enter the user’s home directory and clone the Mastodon Git repository into the
livedirectory:git clone https://github.com/tootsuite/mastodon.git live && cd live
- Check out to the latest stable branch.
git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)
- Install the remaining Ruby dependencies:
bundle config deployment 'true'bundle config without 'development test'bundle install -j$(getconf _NPROCESSORS_ONLN)
- Use yarn to install the node.js dependencies:
yarn install --pure-lockfile
- Type and enter
exitto return to the root account.
Requesting a Let’s Encrypt Certificate
Stop Nginx before requesting the certificate:systemctl stop nginx.service
certbotto request a certficate with TLS SNI validation in standalone mode. Replace
example.comwith your domain name:certbot certonly --standalone -d example.com
As Let’s Encrypt certficates have a validity of 90 days, a cron-job can be used to renew them and to restart nginx automatically.
Create a new file and open it in a text editor like nano:nano /etc/cron.daily/letsencrypt-renew
Copy the following content into the file, save it and exit nano:#!/usr/bin/env bashcertbot renewsystemctl reload nginx.service
Allow execution of the script and restart the cron daemon. It will run the script daily:chmod +x /etc/cron.daily/letsencrypt-renewsystemctl restart cron.service
- Copy the example configuration file shipped with Mastodon in your Nginx
sites-availabledirectory and create a symlink to it in the
sites-enableddirectory:cp /home/mastodon/live/dist/nginx.conf /etc/nginx/sites-available/mastodonln -s /etc/nginx/sites-available/mastodon /etc/nginx/sites-enabled/mastodon
- Open the configuration file in a text editor, such as nano:
- Save and exit.
Configuring the Mastodon Application
mastodonuser account:su - mastodon
Change into the /home/mastodon/live directory and run the Mastodon installer:cd /home/mastodon/liveRAILS_ENV=production bundle exec rake mastodon:setup
The interactive installer guides you through the setup process.
Enter the domain name or subdomain of the instance.
Select No when asked if you want to use Docker.
Most of the other values are already pre-filled with the correct settings. Edit them if required for your setup.
Select Amazon S3 as a service provider to set up Mastodon with Object Storage. Valid API keys are required in this step.
Enter the details as following:Provider Amazon S3S3 bucket name: [scaleway_bucket_name]S3 region: fr-parS3 hostname: s3.fr-par.scw.cloudS3 access key: [scaleway_access_key]S3 secret key: [scaleway_secret_key]Note:
If your bucket is located in Amsterdam, use
nl-amsas region and
s3.nl-ams.scw.cloudas S3 hostname If it is located in Warsaw, use
Once the configuration is complete, the installer will start to compile the application. This may take some time and consume a lot of RAM.
Once the application is installed, you will be asked if you want to create an Administrator account for your Mastodon instance.
Yto create the account. Enter the username for the admin user, followed by your email address. A random password will be generated. Take a note of it, as you will need it to connect to your Instance.All done! You can now power on the Mastodon server 🐘Do you want to create an admin user straight away? YesUsername: admin <-- Enter the username for your Mastodon admin accountE-mail: firstname.lastname@example.org <-- Enter your email addressYou can login with the password: 9dc4d92d93a26e9b6c021bb75b4a3ce2
exitto switch back into the root account.
Setting-up systemd Services
Systemd scripts are used to manage services on Ubuntu systems. Three different scripts are required for Mastodon. These scripts come with the Mastodon package, you need to copy them to their final destination, then activate the services.
- Copy the Mastodon
systemdscripts into their final destination:cp /home/mastodon/live/dist/mastodon-*.service /etc/systemd/system/
- Reload the systemd daemon:
- Start the services and enable them, so they will start automatically upon the next system reboot:
systemctl start mastodon-web.service mastodon-sidekiq.service mastodon-streaming.servicesystemctl enable mastodon-web.service mastodon-sidekiq.service mastodon-streaming.service
- Verify if all services are running:
systemctl status mastodon-*.service
If everything is running, open a web browser and go to your domain name. You will see the home page of your Mastodon instance:
You can log in with the admin account that you have created during the installation to configure additional parameters of your instance, link the instance with another one to join a federated network, create another user account and start sharing posts and photos on your timeline. If configured with Object Storage, all files uploaded to the instance are automatically stored in the Object Storage bucket and embedded in the users timeline:
For more information and advanced configuration of Mastodon, refer to the official documentation.