Difference between revisions of "Alternative startup methods"

From diaspora* project wiki
Jump to: navigation, search
(Removed <code> tags)
(Tags: mobile edit, mobile web edit)
(Example configuration for Debian based systems like Ubuntu 16.04 or Debian 9.0: add reload of diaspora-web.service)
 
Line 56: Line 56:
 
Environment=RAILS_ENV=production
 
Environment=RAILS_ENV=production
 
WorkingDirectory=/home/diaspora/diaspora
 
WorkingDirectory=/home/diaspora/diaspora
 +
PIDFile=/home/diaspora/diaspora/tmp/pids/web.pid
 
ExecStart=/bin/bash -lc "bin/bundle exec unicorn -c config/unicorn.rb -E production"
 
ExecStart=/bin/bash -lc "bin/bundle exec unicorn -c config/unicorn.rb -E production"
 +
ExecReload=/bin/kill -USR2 $MAINPID
 
Restart=always
 
Restart=always
  

Latest revision as of 23:55, 21 June 2018

This page is for listing alternative methods for starting up the Diaspora service automatical or in some manner other than calling the ./script/start

»» Out of date
This page's accuracy may be compromised due to out-of-date information.
Please help improve the page by updating it. There may be additional information on the talk page.
»» Note
Is this still working? If it is, it should be linked in some meaningful places, like FAQ for pod maintainers, Installation guides, or similar.


Init Scripts & Upstart

Sample /etc/diaspora.conf required by the init script is given below

export SERVERNAME=localhost
export ENVIRONMENT_URL=https://localhost
export RAILS_ENV=production
export DB=postgres

systemd

Example configuration for Debian based systems like Ubuntu 16.04 or Debian 9.0

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 unicorn -c config/unicorn.rb -E production"
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

daemontools

god

Passenger

All you need is the following snippet of Apache configuration in e.g. a <VirtualHost> block:

DocumentRoot $diasporapath/public
PassengerAppRoot $diasporapath
PassengerAppEnv production
PassengerRuby $rubypath

Replace $diasporapath with the path where you installed diaspora*, and replace $rubypath with the Ruby binary Passenger should use (probably what RVM installed, if you use RVM).

Note, however, that this does not automatically start Sidekiq. You need to do that yourself.