This uses the Docker version of Pixelfed Glitch, with MariaDB and Redis running as Docker containers.

Contents

Step 1 – Install Docker Step 2 – Allow your user to run Docker Step 3 – Create the Pixelfed Glitch directory Step 4 – Download the Docker files Step 5 – Edit the environment file Step 6 – Prepare Pixelfed's storage directories Step 7 – Start Pixelfed Glitch Step 8 – Generate the application and OAuth keys Step 9 – Stop first-time setup from running again Step 10 – Check the site Step 11 – Create the first user Step 12 – Create another user Step 13 – Useful checks Step 14 – Mobile app login and 2FA Step 15 – Reboot behaviour Step 16 – Backups Troubleshooting notes

Step 1. Install Docker

Pixelfed Glitch will run inside Docker containers. This means we do not need to manually install PHP, MariaDB, Redis, Node, Composer, or most of the other application dependencies on the Raspberry Pi itself.

i. Update the package list:

sudo apt update && sudo apt upgrade

ii. Install the packages needed to add Docker's repository:

sudo apt install -y ca-certificates curl

iii. Create the keyrings directory:

sudo install -m 0755 -d /etc/apt/keyrings

iv. Download Docker's GPG key:

sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc

v. Make the key readable:

sudo chmod a+r /etc/apt/keyrings/docker.asc

vi. Add Docker's repository:

sudo tee /etc/apt/sources.list.d/docker.sources <<EOF
Types: deb
URIs: https://download.docker.com/linux/debian
Suites: $(. /etc/os-release && echo "$VERSION_CODENAME")
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF

vii. Update the package list again:

sudo apt update

viii. Install Docker and the Compose plugin:

sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

ix. Check Docker is running:

sudo systemctl status docker

x. Enable Docker to start at boot:

sudo systemctl enable docker.service
sudo systemctl enable containerd.service

Step 2. Allow your user to run Docker

By default, Docker commands need sudo. To run docker compose as your normal user, add your user to the docker group.

i. Create the group, if it does not already exist:

sudo groupadd docker 2>/dev/null || true

ii. Add your user to it:

sudo usermod -aG docker $USER

iii. Log out of SSH and log back in, or reboot the Pi.

iv. Test Docker without sudo:

docker run hello-world

If this works, Docker is ready.

Step 3. Create the Pixelfed Glitch directory

I installed Pixelfed Glitch under my home directory:

cd /home/pi
mkdir -p pixelfed-glitch
cd pixelfed-glitch

Change /home/pi to match your own username if needed.

Step 4. Download the Docker files

Download the Docker Compose file and the example environment file from the Pixelfed Glitch repository:

curl -fsSL https://raw.githubusercontent.com/pixelfed-glitch/pixelfed/develop/docker-compose.yml -o docker-compose.yml
curl -fsSL https://raw.githubusercontent.com/pixelfed-glitch/pixelfed/develop/.env.docker -o .env

The docker-compose.yml file defines the containers. The .env file holds site-specific settings such as the domain name, database password, upload limits, email settings, and Docker image tags.

Step 5. Edit the environment file

Open the .env file:

nano .env

At minimum, change the following values.

Set the name of the site:

APP_NAME="My Pixelfed Site"

Set the domain name, without https:// and without a trailing slash:

APP_DOMAIN="photos.example.com"

Leave APP_URL like this:

APP_URL="https://${APP_DOMAIN}"

Leave ADMIN_DOMAIN like this:

ADMIN_DOMAIN="${APP_DOMAIN}"

Set a public contact email address:

INSTANCE_CONTACT_EMAIL="admin@example.com"

Set a secure database password:

DB_PASSWORD="CHANGE_THIS_TO_A_LONG_RANDOM_PASSWORD"

If you do not plan to send email at first, you can disable mandatory email verification:

ENFORCE_EMAIL_VERIFICATION="false"

Make sure OAuth is enabled, as this is needed for Pixelfed mobile apps:

OAUTH_ENABLED="true"

Leave APP_KEY empty at this stage:

APP_KEY=

Pixelfed will generate this later. If you ever set it manually, it must be one single Laravel key, for example:

APP_KEY=base64:CHANGE_THIS_TO_ONE_VALID_KEY_ONLY

Do not paste two keys together on the same line.

Step 6. Prepare Pixelfed's storage directories

The Docker image expects several Laravel storage paths to exist. Creating them now avoids a startup error such as:

Please provide a valid cache path.

Run:

cd /home/pi/pixelfed-glitch

sudo mkdir -p docker-compose-state/data/pixelfed/storage/app/public
sudo mkdir -p docker-compose-state/data/pixelfed/storage/framework/cache/data
sudo mkdir -p docker-compose-state/data/pixelfed/storage/framework/sessions
sudo mkdir -p docker-compose-state/data/pixelfed/storage/framework/testing
sudo mkdir -p docker-compose-state/data/pixelfed/storage/framework/views
sudo mkdir -p docker-compose-state/data/pixelfed/storage/logs
sudo mkdir -p docker-compose-state/data/pixelfed/storage/docker/lock
sudo mkdir -p docker-compose-state/data/pixelfed/cache

sudo chown -R 33:33 docker-compose-state/data/pixelfed/storage
sudo chown -R 33:33 docker-compose-state/data/pixelfed/cache

User ID 33 is www-data, which is the user Pixelfed runs as inside the container.

Step 7. Start Pixelfed Glitch

Start the containers:

docker compose up -d

This downloads the Pixelfed Glitch, MariaDB, and Redis images, creates the containers, and starts the first-time setup.

Check the containers:

docker compose ps

You should eventually see web, worker, cron, db, and redis as Up.

To watch the logs:

docker compose logs --tail=100 --follow

If you only want the web container logs:

docker compose logs --tail=100 web

Step 8. Generate the application and OAuth keys

If the site shows a 500 error and the logs mention either of these:

No application encryption key has been specified.
Invalid key supplied

run the following commands:

docker compose exec web php artisan key:generate --force
docker compose exec -u www-data web php artisan passport:keys --force

Then clear and rebuild Pixelfed's cached config:

docker compose exec -u www-data web php artisan view:clear
docker compose exec -u www-data web php artisan config:clear
docker compose exec -u www-data web php artisan cache:clear
docker compose exec -u www-data web php artisan config:cache

Restart the Pixelfed containers:

docker compose restart web worker cron

Step 9. Stop first-time setup from running again

After the first-time setup has completed and the keys have been created, edit .env again:

nano .env

Add this line:

DOCKER_APP_RUN_ONE_TIME_SETUP_TASKS="0"

This stops Pixelfed from trying to recreate encryption keys on every container start.

If this is not set, the container may restart repeatedly with an error like:

Encryption keys already exist. Use the --force option to overwrite them.

Restart the stack:

docker compose down
docker compose up -d

Do not use docker compose down -v, as that removes Docker volumes.

Step 10. Check the site

Open your Pixelfed URL in a browser:

https://photos.example.com

If you are using NGINX as a reverse proxy, make sure it points to the Docker web port. In the default Pixelfed Glitch Docker file this is:

8080

So the proxy target is:

http://127.0.0.1:8080

Check the running containers:

docker compose ps

If you see a 502 error, the web container is probably not running yet, or it is restarting. Check:

docker compose logs --tail=200 web

Step 11. Create the first user

Create the first account:

docker compose exec -u www-data web php artisan user:create

Follow the prompts.

To make the user an admin:

docker compose exec -u www-data web php artisan user:admin USERNAME

To manually verify an email address:

docker compose exec -u www-data web php artisan user:verifyemail USERNAME

For example:

docker compose exec -u www-data web php artisan user:admin rob
docker compose exec -u www-data web php artisan user:verifyemail rob

Step 12. Create another user

Run the same create command again:

docker compose exec -u www-data web php artisan user:create

Follow the prompts and enter the new username.

For example:

bnw

Only run the admin command for accounts that should have admin rights.

Step 13. Useful checks

Check container status:

docker compose ps

Show recent logs:

docker compose logs --tail=200 web

Check the current Pixelfed config values:

docker compose exec -u www-data web php artisan tinker --execute='
echo "app.url=".config("app.url").PHP_EOL;
echo "oauth=".(config("pixelfed.oauth_enabled") ? "true" : "false").PHP_EOL;
echo "session.domain=".config("session.domain").PHP_EOL;
'

Check the application key:

grep '^APP_KEY=' .env

A valid key should look like one single line:

APP_KEY=base64:LONG_RANDOM_STRING_HERE

Check the OAuth key files:

docker compose exec -u www-data web ls -l storage/oauth-private.key storage/oauth-public.key

Step 14. Mobile app login and 2FA

The web version worked fine for me with 2FA enabled.

The mobile app login flow was different. With 2FA enabled, the official Pixelfed app and Impressia both opened a web login pop-up, accepted the username, password, and 2FA code, then stayed in the web version inside the pop-up instead of returning to the app.

The workaround was:

1. Keep 2FA enabled on the admin account.
2. Use a separate non-admin account for mobile app login.
3. Disable 2FA on that non-admin account before logging in to the apps.

If the web interface will not disable 2FA and clicking the green “Enabled” button only adds # to the URL, disable it from the database.

First check the 2FA column names:

docker compose exec -u www-data web php artisan tinker --execute='
print_r(array_values(array_filter(
    Schema::getColumnListing("users"),
    fn($c) => str_contains(strtolower($c), "two") || str_contains(strtolower($c), "2fa") || str_contains(strtolower($c), "otp")
)));
'

On my install the columns were:

2fa_enabled
2fa_secret
2fa_backup_codes
2fa_setup_at

To disable 2FA for a user called bnw:

docker compose exec -u www-data web php artisan tinker --execute='
DB::table("users")->where("username", "bnw")->update([
    "2fa_enabled" => false,
    "2fa_secret" => null,
    "2fa_backup_codes" => null,
    "2fa_setup_at" => null,
]);
echo "2FA disabled for bnw\n";
'

After that, app login worked.

Step 15. Reboot behaviour

The docker-compose.yml file uses:

restart: unless-stopped

This means the containers should come back up after a reboot, as long as Docker itself starts on boot.

Check Docker is enabled:

systemctl is-enabled docker

If needed:

sudo systemctl enable docker

After a reboot, check Pixelfed:

cd /home/pi/pixelfed-glitch
docker compose ps

One thing to remember: if you run this command:

docker compose down

the containers are removed. Docker cannot restart removed containers at boot. To recreate and start them:

cd /home/pi/pixelfed-glitch
docker compose up -d

Step 16. Backups

At minimum, back up the Pixelfed Glitch install directory:

/home/pi/pixelfed-glitch

This contains:

docker-compose.yml
.env
docker-compose-state/

The .env file contains secrets, including the database password and application key, so store backups securely.

The docker-compose-state directory contains the MariaDB data, Redis data, Pixelfed storage, and cache folders. For a live database, a proper database dump is safer than only copying files while containers are running.

A simple manual MariaDB dump can be created with:

cd /home/pi/pixelfed-glitch
docker compose exec db mariadb-dump -u pixelfed -p pixelfed_prod > pixelfed_db_backup.sql

You will be prompted for the database password from .env.

Troubleshooting notes

Docker permission denied Missing cache path Invalid application key First-time setup keeps running

Docker permission denied

If you see:

permission denied while trying to connect to the docker API at unix:///var/run/docker.sock

your user is not in the docker group, or the current login session has not picked up the new group membership.

Fix:

sudo usermod -aG docker $USER

Then log out and back in.

Missing cache path

If the web container restarts and logs show:

Please provide a valid cache path.

create the Laravel storage and cache folders from Step 6.

Invalid application key

If the site shows a 500 error and logs show:

Unsupported cipher or incorrect key length

check .env:

grep '^APP_KEY=' .env

The key must be one single key. It must not look like this:

APP_KEY=base64:KEY_ONE=base64:KEY_TWO

To replace it on a new install:

new_key="base64:$(openssl rand -base64 32)"
sudo sed -i.bak "s|^APP_KEY=.*|APP_KEY=${new_key}|" .env

Then clear the caches:

docker compose exec -u www-data web php artisan view:clear
docker compose exec -u www-data web php artisan config:clear
docker compose exec -u www-data web php artisan cache:clear
docker compose exec -u www-data web php artisan config:cache
docker compose restart web worker cron

First-time setup keeps running

If the web container keeps restarting and logs show:

Encryption keys already exist. Use the --force option to overwrite them.

set this in .env:

DOCKER_APP_RUN_ONE_TIME_SETUP_TASKS="0"

Then restart:

docker compose down
docker compose up -d

Sources: Pixelfed Glitch Docker installation docs Pixelfed Glitch configuration docs Docker Engine Debian installation docs Docker Linux post-installation docs

Tags: #Pixelfed #RaspberryPi

#Climate #EndOfYearReview #F1 #Mastodon #Movies #Pixelfed #RaspberryPi #Science #TV

Contents

Step 1 – Increase the swap file Step 2 – SSH Keys Step 3 – NGINX web server Step 4 – SSL certificates Step 5 – Mastodon pre-installation Step 6 – Install NodeJS Step 7 – Install PostgreSQL (and enable Yarn) Step 8 – Install Ruby Step 9 – Install Mastodon Step 10 – Post-installation customisation

Step 1. Increase the swap file

If you're using a 4GB Raspberry Pi (4B or 5), you will need to increase the size of the swap file, at least temporarily, otherwise the process (in Step 9) to compile CSS/JS assets may crash. Obviously, the 1GB and 2GB models should not be used here as they lack sufficient memory.

You can set the swap file back to its original size—once Mastodon is installed—by following these steps again, but this is not necessary.

⚠️  If you're using a Raspberry Pi (4B or 5) with 8GB of RAM, you can safely skip this and move straight on to Step 2.

1. Stop the system from using the current swap file:

   sudo dphys-swapfile swapoff

2. Open the swap file configuration file:

   sudo nano /etc/dphys-swapfile

3. Find the following line of text within the file (value may vary):

   CONF_SWAPSIZE=200

   and change the value to 2048 (MB):

   CONF_SWAPSIZE=2048

4. Save the file by pressing CTRL + X, followed by Y, then Enter.

5. Re-initialise the swap file (removes the original swap file and recreates it to fit the newly defined size):

   sudo dphys-swapfile setup

6. Turn the swap back on:

   sudo dphys-swapfile swapon

7. Reboot the device to allow all programs to be reloaded with access to the new memory pool:

   sudo reboot

Step 2. SSH Keys

Using SSH keys for authentication instead of passwords is a great way of securing the Raspberry Pi, as well as making logins much quicker.

1. Find your public SSH key on your computer. On macOS, this will be a file ending .pub in the ~/.ssh directory.

2. Create a .ssh directory in your home directory on the Raspberry Pi:

   install -d -m 700 ~/.ssh

3. Create (and edit) an authorized_keys file in the new directory:

   nano ~/.ssh/authorized_keys

4. Paste the contents of your public SSH key into this file, then save.

5. Ensure the file has the correct permissions:

   sudo chmod 644 ~/.ssh/authorized_keys

6. Ensure the file has the correct owner (if not using pi as the default user, replace it below with the name of your default user):

   sudo chown pi:pi ~/.ssh/authorized_keys

Step 3. NGINX web server

We want the ability to host other websites on this server so we will use NGINX as a reverse proxy for Mastodon.

1. Update the package list and upgrade existing packages:

   sudo apt update && sudo apt upgrade

2. Install NGINX:

   sudo apt install -y nginx

3. Start the NGINX service:

   sudo systemctl start nginx

4. Install PHP-FPM and recommended PHP modules:

   sudo apt install -y php8.2-fpm php8.2-mbstring php8.2-mysql php8.2-curl php8.2-gd php8.2-zip php8.2-xml

Step 4. SSL certificates

I am using Cloudflare for DNS and tunnelling so I need to follow these steps to create and deploy an Origin CA certificate.

⚠️  If you don't use Cloudflare, install your own SSL certificate here instead of following the exact instructions below.

1. Log in to the Cloudflare dashboard and select an account.

2. Choose your domain.

3. Go to SSL/TLS > Origin Server.

4. Select Create Certificate.

5. Choose Generate private key and CSR with Cloudflare and leave all other options as they are. Click the Create button.

6. Ensure the Key Format is PEM and then copy the signed Origin Certificate and Private Key into separate .pem and .key files. Click the OK button.

7. Copy the .pem and .key files to your Raspberry Pi in the /etc/ssl directory.

8. Change the owner of both files to root:

   sudo chown root:root /etc/ssl/filename.key /etc/ssl/filename.pem

9. Restart NGINX:

   sudo systemctl restart nginx

10. Back in the Cloudflare dashboard, go to SSL/TLS > Overview and click Configure. Under the option Custom SSL/TLS click Select. Change the option to Full (Strict) and click Save.

Step 5. Mastodon pre-installation

1. Update and upgrade system packages:

   sudo apt update && sudo apt upgrade

2. Install dependencies:

   sudo apt install -y curl lsb-release 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 libgdbm-dev nginx redis-server redis-tools certbot python3-certbot-nginx libidn11-dev libicu-dev libjemalloc-dev

3. Create a mastodon user:

   sudo useradd mastodon -m

Step 6. Install NodeJS

1. Update the package list and upgrade existing packages:

   sudo apt update && sudo apt upgrade

2. To ensure we have all of the packages we need to access the Nodesource repository, run the following command:

   sudo apt install -y ca-certificates curl gnupg

3. Download the Nodesource GPG key and store it within the /usr/share/keyrings directory:

   curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/nodesource.gpg

4. Set an environment variable that we will reference next:

   NODE_MAJOR=20

5. Add the NodeJS repository to your sources list:

   echo "deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_$NODE_MAJOR.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list

6. Since we made changes to the sources list, we need to update the package list:

   sudo apt update

7. Install the NodeJS package:

   sudo apt install -y nodejs

Step 7. Install PostgreSQL (and enable Yarn)

1. Save the GPG key for the PostgreSQL repository:

   curl -L https://www.postgresql.org/media/keys/ACCC4CF8.asc | gpg --dearmor | sudo tee /usr/share/keyrings/postgresql-archive-keyring.gpg >/dev/null

2. Add the repository to our sources list:

   echo "deb [arch=arm64 signed-by=/usr/share/keyrings/postgresql-archive-keyring.gpg] http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" | sudo tee  /etc/apt/sources.list.d/postgresql.list

3. As we changed the available repositories, we need to update the package list cache again:

   sudo apt update

4. Install the PostgreSQL package:

   sudo apt install -y postgresql postgresql-contrib

5. Launch the PostgreSQL command line interface (CLI):

   sudo -u postgres psql

6. Create a PostgreSQL user named mastodon:

   CREATE USER mastodon CREATEDB;

7. Quit out of the CLI:

   \q

8. To build and run Mastodon, we need to enable Yarn (the NodeJS package manager). Do this now:

   sudo corepack enable && sudo yarn set version classic

Step 8. Install Ruby

1. Switch to the mastodon user:

   sudo su mastodon

2. Change to the home directory:

   cd ~

3. Clone the code repository for the rbenv utility:

   git clone https://github.com/rbenv/rbenv.git ~/.rbenv

4. Clone the code repository for the ruby-build plugin:

   git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build

5. Adjust the .bashrc file to initialise the rbenv utility to set up the Ruby environment:

   echo 'eval "$(~/.rbenv/bin/rbenv init - bash)"' >> ~/.bashrc

6. To ensure the changes we made are available immediately:

   exec bash

7. Install Ruby 3.3.5:

   RUBY_CONFIGURE_OPTS=--with-jemalloc rbenv install 3.3.5

   ⚠️  This step can take a long time to complete.

8. Declare the installed Ruby version 3.3.5 as the global version to use:

   rbenv global 3.3.5

9. Use the Ruby package manager to install bundler:

   gem install bundler --no-document

Step 9. Install Mastodon

1. Make sure that you are still running as the mastodon user; switch to that user now, if not:

   sudo su mastodon

2. Change to the home directory:

   cd ~

3. Clone the code repository for Mastodon, then change to the new live directory:

   git clone https://github.com/mastodon/mastodon.git live && cd live

4. Change to the latest stable release of Mastodon:

   git checkout $(git tag -l | grep '^v[0-9.]*$' | sort -V | tail -n 1)

5. Set the deployment option to true and exclude any packages that are only used for development or test purposes:

   bundle config deployment 'true' && bundle config without 'development test'

6. Install all of the Ruby dependencies for Mastodon:

   bundle install -j$(nproc)

   Note: we use the -j option to tell the package manager to use as many CPU cores as we have.

7. Install all of the NodeJS dependencies for Mastodon:

   yarn install

   ⚠️  You can safely ignore any warnings thrown here.

8. Configure Mastodon:

   RAILS_ENV=production bundle exec rake mastodon:setup

9. Follow the on-screen prompts for how you would like to set up Mastodon. You can leave the PostgreSQL and Redis options as default (just press Enter on each option).

10. Switch back to your default user:

    exit

11. Update the default NGINX host file using the template provided on the Mastodon docs website, or replace the file with a copy of a previously backed-up host file.

12. Reload NGINX web server:

    sudo systemctl reload nginx

13. Copy the systemd services for Mastodon to the relevant directory:

    sudo cp /home/mastodon/live/dist/mastodon-*.service /etc/systemd/system/

14. Start the services now and enable them to start automatically at logon in future:

    sudo systemctl enable --now mastodon-web mastodon-sidekiq mastodon-streaming

Step 10. Post-installation customisation (optional)

Import a blocklist Change the maximum post length and poll limit Change the username, display name, and notes limits

Import a blocklist

1. Download this blocklist.

2. In Mastodon, go to Moderation > Federation and click on the Import button at the top of the page.

3. Choose the blocklist file you previously downloaded and click Upload.

4. You should now see a long list of domain blocks. Make sure the Select All checkbox is selected and then click on Import.

Change the maximum post length and poll limit

1. Switch to the mastodon user:

   sudo su mastodon

2. Change to the home directory:

   cd ~

3. Edit the compose_form_container.js file:

   nano -w live/app/javascript/mastodon/features/compose/containers/compose_form_container.js

4. Search for the line:

   maxChars: state.getIn(['server', 'server', 'configuration', 'statuses', 'max_characters'], 500)

   and change the value 500 to the new limit (e.g. 2000).

5. Save the file by pressing CTRL + X, followed by Y, then Enter.

6. Edit the status_length_validator.rb file:

   nano -w live/app/validators/status_length_validator.rb

7. Search for the line:

   MAX_CHARS = 500

   and change the value 500 to the same new limit as above.

8. Save the file by pressing CTRL + X, followed by Y, then Enter.

9. Edit the poll_options_validator.rb file:

   nano -w live/app/validators/poll_options_validator.rb

10. Search for the line:

    MAX_OPTIONS = 4

    and change the value 4 to the new limit (e.g. 12).

11. Save the file by pressing CTRL + X, followed by Y, then Enter.

12. Rebuild the assets:

    cd live && RAILS_ENV=production bundle exec rails assets:precompile

13. Switch back to the main user:

    exit

14. Restart the Mastodon services:

    sudo systemctl restart mastodon-sidekiq mastodon-web mastodon-streaming

Change the username, display name, and notes limits

1. Switch to the mastodon user:

   sudo su mastodon

2. Change to the home directory:

   cd ~

3. Edit the account.rb file:

   nano -w live/app/models/account.rb

4. Search for the following lines and amend as required:

   USERNAME_LENGTH_LIMIT = 30

   DISPLAY_NAME_LENGTH_LIMIT = 30

   NOTE_LENGTH_LIMIT = 500

5. Save the file by pressing CTRL + X, followed by Y, then Enter.

6. Restart the Mastodon services:

   sudo systemctl restart mastodon-sidekiq mastodon-web mastodon-streaming

Sources: Increasing Swap on a Raspberry Pi How to Setup SSH Keys on your Raspberry Pi Build your own Raspberry Pi NGINX Web Server Cloudflare origin CA How to create a CSR using OpenSSL & install your SSL certificate on a Nginx server Installing Mastodon on the Raspberry Pi Installing NodeJS on the Raspberry Pi Mastodon blocklists Increasing the Mastodon post character and poll options limit

Tags: #Mastodon #RaspberryPi