Template:Installation/Common: Difference between revisions

From diaspora* project wiki
(→‎Bundle: Explain how to handle the sigar build issue.)
(Add reverse proxy section to the bottom of the guide)
 
(28 intermediate revisions by 9 users not shown)
Line 5: Line 5:
{{#tag:syntaxhighlight|
{{#tag:syntaxhighlight|
cd ~
cd ~
git clone {{#ifeq: {{#var:mode}}|production|-b master|}} https://github.com/diaspora/diaspora.git
git clone {{#ifeq: {{#var:mode}}|production|-b main|}} https://github.com/diaspora/diaspora.git
cd diaspora
cd diaspora
|lang=bash}}
|lang=bash}}
Line 17: Line 17:
{{#tag:syntaxhighlight|
{{#tag:syntaxhighlight|
cp config/database.yml.example config/database.yml
cp config/database.yml.example config/database.yml
cp config/diaspora.yml.example config/diaspora.yml
cp config/diaspora.toml.example config/diaspora.toml
|lang=bash}}
|lang=bash}}


{{#ifeq: {{#var:mode}}|production|{{Template:Installation/Configuration}}
{{#ifeq: {{#var:mode}}|production|{{Template:Installation/Configuration}}|}}
{{Installation/Reverse_proxy}}|}}
 
== Bundle ==
== Bundle ==


Line 27: Line 27:


{{#tag:syntaxhighlight|
{{#tag:syntaxhighlight|
gem install bundler
script/configure_bundler
{{#ifeq:{{#var:gcc5}}|true|bundle config --local build.sigar '--with-cppflags="-fgnu89-inline"'
bin/bundle install --full-index
<nowiki/>|}}{{#ifeq:{{#var:dist}}{{#var:version}}{{#varDB}}|CentOS6postgres|bundle config --local build.pg '--with-pg-config=/usr/pgsql-<version>/bin/pg_config'
<nowiki/>}}{{#var:env_string}}bin/bundle install {{#ifeq:{{#var:mode}}|production| --jobs $(nproc) --deployment --without test development|}} --with {{#switch: {{#var:DB}}|mysql=mysql|postgres=postgresql|mariadb=mysql}}
|lang=bash}}
|lang=bash}}


This takes quite a while. When it's finished, you should see a message similar to: <tt>Bundle complete! 137 Gemfile dependencies, 259 gems now installed.</tt> If that's not the case, you should seek for help on the mailing list or the IRC channel. The <tt>--jobs $(nproc)</tt> flag speeds things a bit since it enables parallel downloading. <tt>nproc</tt> shows the number of CPU cores you have available.
This takes quite a while. When it's finished, you should see a message similar to: <tt>Bundle complete! 137 Gemfile dependencies, 259 gems now installed.</tt> If that's not the case, you should seek for help on the mailing list or the IRC channel.


Running the manual <tt>gem install</tt> command shown in the error message can sometimes show a clearer error message if the <tt>bundle</tt> command fails.
Running the manual <tt>gem install</tt> command shown in the error message can sometimes show a clearer error message if the <tt>bundle</tt> command fails.
{{#ifeq: {{#var:version}}|Wheezy||Note: If you are installing on testing/stretch, you will need to rebuild the sigar gem.  To do this, you need to run:
<syntaxhighlight lang="bash">
GEM_HOME=vendor/bundle/ruby/2.3.0 gem uninstall sigar
bundle config --local build.sigar '--with-cppflags="-fgnu89-inline"'
</syntaxhighlight>
Afterwards, you need to re-run the <tt>bundle install</tt> command.
(It might be possible to run this sigar build prior to running the initial <tt>bundle install</tt> command, but this has not been tested.)}}


== Database setup ==
== Database setup ==
Line 53: Line 40:


{{#tag:syntaxhighlight|
{{#tag:syntaxhighlight|
{{#var:env_string}}bin/rake db:create db:schema:load
{{#var:env_string}}bin/rake db:create db:migrate
|lang=bash}}
|lang=bash}}
{{#ifeq: {{#var:mode}}|production|{{Installation/Assets}}|}}
{{#ifeq: {{#var:mode}}|production|{{Installation/Assets}}|}}
== Start diaspora* ==
== Start diaspora* ==


Line 64: Line 52:
|lang="bash"}}
|lang="bash"}}


{{#ifeq: {{#var:mode}}|production|In the most simple case you want to do this inside a [http://www.gnu.org/software/screen/ screen] or [http://tmux.sourceforge.net/ tmux] session from which you can safely detach.|}}
Your diaspora server is now running, either on a unix socket (current default) or on http port 3000. The listening method can be configured in diaspora.toml, search for '3000' or 'listen' to find the correct line.
 
{{#ifeq: {{#var:mode}}|production|
The server script is good to ensure your server works as expected. You should set up [[Automatic_startup_methods|automatic startup]] for your pod, so that your pod automatically starts on server reboots, and recovers from eventual crashes.
{{Installation/Reverse_proxy}}
|}}
 
== Backup ==
{{Serious|1=You have to do backups of your pod data. If you lose your data, you won't be able to use the combination of your old username and old domain ever again. Make sure to store the backups on a different server, or at least on a different hard drive.<br />For details on how to do backups, see [[Pod data backup]].}}


== Further reading ==
== Further reading ==

Latest revision as of 23:11, 15 June 2024

Get the source

It's time to download diaspora*! As your diaspora user run:

cd ~
git clone  https://github.com/diaspora/diaspora.git
cd diaspora

Don't miss the cd diaspora, all coming commands expect to be run from that directory!

Configuration

Copy files

cp config/database.yml.example config/database.yml
cp config/diaspora.toml.example config/diaspora.toml


Bundle

It's time to install the Ruby libraries required by diaspora*:

script/configure_bundler
bin/bundle install --full-index

This takes quite a while. When it's finished, you should see a message similar to: Bundle complete! 137 Gemfile dependencies, 259 gems now installed. If that's not the case, you should seek for help on the mailing list or the IRC channel.

Running the manual gem install command shown in the error message can sometimes show a clearer error message if the bundle command fails.

Database setup

Double check your config/database.yml looks right and run:

bin/rake db:create db:migrate


Start diaspora*

It's time to start diaspora*:

./script/server

Your diaspora server is now running, either on a unix socket (current default) or on http port 3000. The listening method can be configured in diaspora.toml, search for '3000' or 'listen' to find the correct line.


Backup

WarningWarning:You have to do backups of your pod data. If you lose your data, you won't be able to use the combination of your old username and old domain ever again. Make sure to store the backups on a different server, or at least on a different hard drive.
For details on how to do backups, see Pod data backup.

Further reading