changelog: add entry

CHANGELOG.md

@@ -29,6 +29,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 - MastoAPI: Support for `birthday` and `show_birthday` field in `/api/v1/accounts/update_credentials`.
 - Configuration: Add `birthday_required` and `birthday_min_age` settings to provide a way to require users to enter their birth date.
 - PleromaAPI: Add `GET /api/v1/pleroma/birthdays` API endpoint
+- systemd template service unit
 
 ### Fixed
 - Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies

docs/administration/backup.md

@@ -32,8 +32,8 @@
 1. Optionally you can remove the users of your instance. This will trigger delete requests for their accounts and posts. Note that this is 'best effort' and doesn't mean that all traces of your instance will be gone from the fediverse.
     * You can do this from the admin-FE where you can select all local users and delete the accounts using the *Moderate multiple users* dropdown.
     * You can also list local users and delete them individualy using the CLI tasks for [Managing users](./CLI_tasks/user.md).
-2. Stop the Pleroma service `systemctl stop pleroma`
-3. Disable pleroma from systemd `systemctl disable pleroma`
+2. Stop the Pleroma service `systemctl stop pleroma@prod`
+3. Disable pleroma from systemd `systemctl disable pleroma@prod`
 4. Remove the files and folders you created during installation (see installation guide). This includes the pleroma, nginx and systemd files and folders.
 5. Reload nginx now that the configuration is removed `systemctl reload nginx`
 6. Remove the database and database user `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;';` `sudo -Hu postgres psql -c 'DROP USER <pleroma_db>;'`

docs/configuration/hardening.md

@@ -64,7 +64,7 @@ If you click on a link, your browser’s request to the other site will include
 
 ## systemd
 
-A systemd unit example is provided at `installation/pleroma.service`.
+A systemd unit example is provided at `installation/pleroma@.service`.
 
 ### PrivateTmp
 

docs/configuration/onion_federation.md

@@ -56,7 +56,7 @@ exit
 ```
 restart Pleroma (if using systemd):
 ```
-systemctl restart pleroma
+systemctl restart pleroma@prod
 ```
 
 # Tor Instance Access

docs/installation/arch_linux_en.md

@@ -194,14 +194,14 @@ You can find example configurations for them in `/opt/pleroma/installation/`.
 * Copy example service file
 
 ```shell
-sudo cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
+sudo cp /opt/pleroma/installation/pleroma@.service /etc/systemd/system/pleroma@.service
 ```
 
 * Edit the service file and make sure that all paths fit your installation
-* Enable and start `pleroma.service`:
+* Enable and start `pleroma@prod.service`:
 
 ```shell
-sudo systemctl enable --now pleroma.service
+sudo systemctl enable --now pleroma@prod.service
 ```
 
 #### Create your first user

docs/installation/debian_based_en.md

@@ -157,14 +157,14 @@ You can find example configurations for them in `/opt/pleroma/installation/`.
 * Copy example service file
 
 ```shell
-sudo cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
+sudo cp /opt/pleroma/installation/pleroma@.service /etc/systemd/system/pleroma@.service
 ```
 
 * Edit the service file and make sure that all paths fit your installation
-* Enable and start `pleroma.service`:
+* Enable and start `pleroma@prod.service`:
 
 ```shell
-sudo systemctl enable --now pleroma.service
+sudo systemctl enable --now pleroma@prod.service
 ```
 
 #### Create your first user

docs/installation/debian_based_jp.md

@@ -166,13 +166,13 @@ sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /
 
 * サービスファイルのサンプルをコピーします。
 ```
-sudo cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
+sudo cp /opt/pleroma/installation/pleroma@.service /etc/systemd/system/pleroma@.service
 ```
 
 * サービスファイルを変更します。すべてのパスが正しいことを確認してください
-* サービスを有効化し `pleroma.service` を開始してください
+* サービスを有効化し `pleroma@prod.service` を開始してください
 ```
-sudo systemctl enable --now pleroma.service
+sudo systemctl enable --now pleroma@prod.service
 ```
 
 #### 初期ユーザの作成

docs/installation/migrating_from_source_otp_en.md

@@ -125,16 +125,16 @@ OTP releases have different service files than from-source installs so they need
 === "Debian/Ubuntu"
     ```sh
     # Copy the service into a proper directory
-    cp ~pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
+    cp ~pleroma/installation/pleroma@.service /etc/systemd/system/pleroma@.service
 
     # Reload service files
     systemctl daemon-reload
 
     # Reenable pleroma to start on boot
-    systemctl reenable pleroma
+    systemctl reenable pleroma@prod
 
     # Start pleroma
-    systemctl start pleroma
+    systemctl start pleroma@prod
     ```
 
 ## Running mix tasks

docs/installation/otp_en.md

@@ -226,11 +226,11 @@ At this point if you open your (sub)domain in a browser you should see a 502 err
 === "Debian/Ubuntu"
     ```
     # Copy the service into a proper directory
-    cp /opt/pleroma/installation/pleroma.service /etc/systemd/system/pleroma.service
+    cp /opt/pleroma/installation/pleroma@.service /etc/systemd/system/pleroma@.service
 
     # Start pleroma and enable it on boot
-    systemctl start pleroma
-    systemctl enable pleroma
+    systemctl start pleroma@prod
+    systemctl enable pleroma@prod
     ```
 
 If everything worked, you should see Pleroma-FE when visiting your domain. If that didn't happen, try reviewing the installation steps, starting Pleroma in the foreground and seeing if there are any errrors.

installation/pleroma@.service

@@ -1,5 +1,5 @@
 [Unit]
-Description=Pleroma social network
+Description=Pleroma social network (MIX_ENV=%i)
 After=network.target postgresql.service
 
 [Service]
@@ -10,7 +10,7 @@ Restart=on-failure
 ; Name of the user that runs the Pleroma service.
 User=pleroma
 ; Declares that Pleroma runs in production mode.
-Environment="MIX_ENV=prod"
+Environment="MIX_ENV=%i"
 
 ; Make sure that all paths fit your installation.
 ; Path to the home directory of the user running the Pleroma service.