Automatic startup methods: Difference between revisions
m (DenSchub moved page Alternative startup methods to Automatic startup methods) |
No edit summary |
||
Line 1: | Line 1: | ||
This page is for listing | This page is for listing methods to automatically start diaspora* when your server starts. | ||
= Recommend: systemd = | |||
Paste the following systemd unit file into ''/etc/systemd/system/diaspora.service'': | |||
<pre> | |||
[Unit] | |||
Description=Diaspora social network | |||
After=network.target | |||
[Service] | |||
User=diaspora | |||
WorkingDirectory=/home/diaspora/diaspora | |||
ExecStart=/bin/bash -lc "script/server" | |||
Restart=always | |||
[Install] | |||
WantedBy=multi-user.target | |||
</pre> | |||
When the file is saved, you can start your pod with ''systemctl enable --now diaspora.service'', and the pod will automatically start again if you restart your server. | |||
= Alternatives = | |||
These are possible alternatives, use them only if you have a specific need. | |||
== systemd with individual services == | == systemd with individual services == |
Revision as of 00:27, 9 June 2024
This page is for listing methods to automatically start diaspora* when your server starts.
Recommend: systemd
Paste the following systemd unit file into /etc/systemd/system/diaspora.service:
[Unit] Description=Diaspora social network After=network.target [Service] User=diaspora WorkingDirectory=/home/diaspora/diaspora ExecStart=/bin/bash -lc "script/server" Restart=always [Install] WantedBy=multi-user.target
When the file is saved, you can start your pod with systemctl enable --now diaspora.service, and the pod will automatically start again if you restart your server.
Alternatives
These are possible alternatives, use them only if you have a specific need.
systemd with individual services
This configuration is based on a forum post of Benjamin Neff [1]
cd /etc/systemd/system
Create the following files with you preferred text editor e.g. nano
diaspora.target
[Unit] Description=Diaspora social network Wants=postgresql.service Wants=redis-server.service After=redis-server.service After=postgresql.service [Install] WantedBy=multi-user.target
diaspora-web.service
[Unit] Description=Diaspora social network (unicorn) PartOf=diaspora.target StopWhenUnneeded=true [Service] User=diaspora Environment=RAILS_ENV=production WorkingDirectory=/home/diaspora/diaspora PIDFile=/home/diaspora/diaspora/tmp/pids/web.pid ExecStart=/bin/bash -lc "bin/bundle exec puma -C config/puma.rb" ExecReload=/bin/kill -USR2 $MAINPID Restart=always [Install] WantedBy=diaspora.target
diaspora-sidekiq.service
[Unit] Description=Diaspora social network (sidekiq) PartOf=diaspora.target StopWhenUnneeded=true [Service] User=diaspora Environment=RAILS_ENV=production WorkingDirectory=/home/diaspora/diaspora ExecStart=/bin/bash -lc "bin/bundle exec sidekiq" Restart=always [Install] WantedBy=diaspora.target
Now you have to enable all of them
systemctl enable diaspora.target diaspora-sidekiq.service diaspora-web.service
Start all services with
systemctl restart diaspora.target
You can check if unicorn and sidekiq work with
systemctl status diaspora-web.service systemctl status diaspora-sidekiq.service
Hint: The path /lib/systemd/system/ is for unit-files installed from the system, you can create user-created units in /etc/systemd/system/. Both locations work.
Other sources
- Old systemd unit starting script/server
- modular systemd units (running puma instead of unicorn and chruby instead of RVM)