Automatic startup methods: Difference between revisions

Revision as of 01:16, 30 August 2015

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

Init Scripts & Upstart

Init script of debian-installer package

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

Old systemd unit starting script/server
modular systemd units (running puma instead of unicorn)

daemontools

Unmaintained scripts to start foreman directly

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.

@@ Line 26: / Line 26: @@
 * [https://github.com/despora/diaspora/blob/despora/script/diaspora.god Despora god config]
 * [https://github.com/diasporg/diaspora/blob/master/script/diaspora.god diasp.org god config]
+== Passenger ==
+All you need is the following snippet of Apache configuration in e.g. a <code><VirtualHost></code> block:
+<code><pre>
+DocumentRoot $diasporapath/public
+PassengerAppRoot $diasporapath
+PassengerAppEnv production
+PassengerRuby $rubypath
+</pre></code>
+Replace <code>$diasporapath</code> with the path where you installed diaspora*, and replace <code>$rubypath</code> 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.