Difference between revisions of "Alternative startup methods"

From diaspora* project wiki
Jump to: navigation, search
(Add instructions for Passenger)
(systemd)
Line 18: Line 18:
 
== systemd ==
 
== systemd ==
 
* [https://github.com/jhass/diaspora/blob/old_systemd/diaspora.service Old systemd unit starting script/server]
 
* [https://github.com/jhass/diaspora/blob/old_systemd/diaspora.service Old systemd unit starting script/server]
* [https://github.com/jhass/diaspora/tree/systemd/systemd modular systemd units] (running puma instead of unicorn)
+
* [https://github.com/jhass/diaspora/tree/systemd/systemd modular systemd units] (running puma instead of unicorn and chruby instead of RVM)
  
 
== daemontools ==
 
== daemontools ==

Revision as of 01:38, 13 November 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

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

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.