Difference between revisions of "Diaspora"

From ArchWiki
Jump to: navigation, search
m
(Changed to newly supported Ruby version 2.2)
 
(21 intermediate revisions by 11 users not shown)
Line 1: Line 1:
[[Category:Networking]]
+
[[Category:Web server]]
[http://www.joindiaspora.com/ Diaspora] is the privacy aware, personally controlled, do-it-all, open source social network.
+
[http://www.diasporafoundation.org/ Diaspora] is the privacy aware, personally controlled, do-it-all, open source social network.
  
On November 23, 2010 was [http://blog.joindiaspora.com/2010/11/23/private-alpha-released.html announced] that Diaspora is in [http://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha private alpha] phase.
+
On November 23, 2010 was [http://blog.joindiaspora.com/2010/11/23/private-alpha-released.html announced] that Diaspora is in [[wikipedia:Software_release_life_cycle#Alpha|private alpha]] phase.
  
 
Since August 27, 2012 Diaspora is ruled by the community ([http://blog.diasporafoundation.org/2012/08/27/announcement-diaspora-will-now-be-a-community-project.html announcement]).
 
Since August 27, 2012 Diaspora is ruled by the community ([http://blog.diasporafoundation.org/2012/08/27/announcement-diaspora-will-now-be-a-community-project.html announcement]).
 
  
 
== Prerequisites ==
 
== Prerequisites ==
* Since Diaspora can run on MySQL and PostgreSQL you need to decide which one you want to use. Install one of them and set it up.
+
 
* Diaspora starts a so called appserver, on port 3000 by default, which serves the dynamic contents. You need a reverse proxy to handle the static content that forwards requests it can't handle to the appserver. Typical tools for that are Apache or Nginx.
+
* Since Diaspora can run on [[MySQL]] and [[PostgreSQL]] you need to decide which one you want to use. Install one of them and set it up.
 +
* Diaspora starts a so called appserver, on port 3000 by default, which serves the dynamic contents. You need a reverse proxy to handle the static content and that forwards requests it can't handle to the appserver. Typical tools for that are [[Apache]] or [[Nginx]].
 
* You'll also need the usual tools to build packages from the AUR.
 
* You'll also need the usual tools to build packages from the AUR.
* And [https://aur.archlinux.org/packages/ruby-bundler/ ruby-bundler] from the AUR.
+
* And {{AUR|ruby2.2}} and {{AUR|ruby2.2-bundler}} from the AUR.
  
 
== Installation ==
 
== Installation ==
  
Obtain the [https://aur.archlinux.org/packages/diaspora/ diaspora] package from the AUR, do not use any AUR helpers such as yaourt to build the package, since it's a split package and you want only one part. So, for example if you use Yaourt run:
+
Install {{AUR|diaspora-mysql}} or {{AUR|diaspora-postgresql}} from the AUR.
yaourt -G diaspora && cd diaspora
+
  
To build and install the MySQL version run:
+
Now edit  {{ic|/etc/webapps/diaspora/database.yml}} and fill out the needed values. Then edit {{ic|/etc/webapps/diaspora/diaspora.yml}} and change at least the url setting to the URL your installation will be reachable under (the one served by your reverse proxy). You can change the port the appserver will listen on under the server section. By default Diaspora requires a SSL setup, you can disable that with the require_ssl setting.
makepkg -si --pkg diaspora-mysql
+
 
+
To build and install the PostgreSQL version run:
+
  makepkg -si --pkg diaspora-postgresql
+
 
+
Now edit  /etc/webapps/diaspora/database.yml and fill out the needed values. Then edit /etc/webapps/diaspora/diaspora.yml and change at least the url setting to the URL your installation will be reachable under (the one served by your reverse proxy). You can change the port the appserver will listen on under the server section. By default Diaspora requires a SSL setup, you can disable that with the require_ssl setting.
+
  
 
Ensure your database is running and then switch to the diaspora user:
 
Ensure your database is running and then switch to the diaspora user:
  sudo -u diaspora /bin/bash
+
$ su diaspora
  cd $HOME
+
$ cd
  
 
Create the database and initialize the schema:
 
Create the database and initialize the schema:
   bundle exec rake db:create db:schema:load
+
   bin/bundle exec rake db:create db:schema:load
 
If the user you specified in the database.yml file can't create databases leave the 'db:create' out and create a database named diaspora_production by hand.
 
If the user you specified in the database.yml file can't create databases leave the 'db:create' out and create a database named diaspora_production by hand.
  
You can now switch back to your regular user and start Diaspora:
+
You can now switch back to your regular user and start '''diaspora''' [[systemd]] service.
  sudo systemctl start diaspora
+
  
The static content your reverse proxy needs to serve will be available under /usr/share/webapps/diaspora/public/
+
The static content your reverse proxy needs to serve will be available under {{ic|/usr/share/webapps/diaspora/public/}}
  
 
== Updating ==
 
== Updating ==
  
 
Updating is very analogous. Obtain the newest version of the package and build it, just like in the installation instructions. Watch for .pacnew files and review the changes. Also read the [https://github.com/diaspora/diaspora/blob/master/Changelog.md changelog] over at Diaspora. Then again ensure the database is running and switch to the diaspora user:
 
Updating is very analogous. Obtain the newest version of the package and build it, just like in the installation instructions. Watch for .pacnew files and review the changes. Also read the [https://github.com/diaspora/diaspora/blob/master/Changelog.md changelog] over at Diaspora. Then again ensure the database is running and switch to the diaspora user:
   sudo -u diaspora /bin/bash
+
   $ su diaspora
   cd $HOME
+
   $ cd
  
 
And update the database schema:
 
And update the database schema:
   bundle exec rake db:migrate
+
   bin/bundle exec rake db:migrate
  
Exit and restart Diaspora:
+
Exit and restart '''diaspora''' systemd service.
  sudo systemctl restart diaspora
+
  
 +
If you notice [https://wiki.diasporafoundation.org/FAQ_for_pod_maintainers#I_installed_diaspora.2A_on_my_machine.2C_but_when_I_load_the_site_there_are_no_images_and_the_layout_looks_horrible.21 missing icons or layout issues] after restarting the service, switch to the diaspora user again and run:
 +
 +
  bin/bundle exec rake assets:precompile
 +
 +
Once more, exit and restart '''diaspora''' systemd service.
  
 
== Add yourself as an admin ==
 
== Add yourself as an admin ==
  
 
Switch to the diaspora user and start the Rails console:
 
Switch to the diaspora user and start the Rails console:
   sudo -u diaspora /bin/bash
+
   su diaspora
   cd $HOME
+
   cd
   bundle exec rails console production
+
   bin/bundle exec rails console production
  
Then run the following command, replacing "user" with your username:
+
Then run the following command, replacing ''user'' with your username:
   Role.add_admin User.find_by_username("user")
+
   Role.add_admin User.where(username: "user").first.person
  
You can exit the Rails console by pressing Ctrl+D.
+
You can exit the Rails console by pressing {{ic|Ctrl+d}}.
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
===GDM login screen with diaspora===
+
=== GDM login screen with Diaspora ===
 +
 
 
GDM will insert the user diaspora in its login window because it currently considers the id range 500-1000 as normal users while Arch considers this range for system users as defined in /etc/login.defs. GDM does that probably to keep legacy normal users working.
 
GDM will insert the user diaspora in its login window because it currently considers the id range 500-1000 as normal users while Arch considers this range for system users as defined in /etc/login.defs. GDM does that probably to keep legacy normal users working.
 
To exclude this user from the login window, add this 'Exclude' line in your /etc/gdm/custom.conf file:
 
To exclude this user from the login window, add this 'Exclude' line in your /etc/gdm/custom.conf file:
Line 72: Line 69:
 
  Exclude=diaspora
 
  Exclude=diaspora
  
==More Resources==
+
== See also ==
*[http://github.com/diaspora/diaspora Diaspora git]
+
 
 +
* [http://github.com/diaspora/diaspora Diaspora git]

Latest revision as of 14:51, 19 March 2016

Diaspora is the privacy aware, personally controlled, do-it-all, open source social network.

On November 23, 2010 was announced that Diaspora is in private alpha phase.

Since August 27, 2012 Diaspora is ruled by the community (announcement).

Prerequisites

  • Since Diaspora can run on MySQL and PostgreSQL you need to decide which one you want to use. Install one of them and set it up.
  • Diaspora starts a so called appserver, on port 3000 by default, which serves the dynamic contents. You need a reverse proxy to handle the static content and that forwards requests it can't handle to the appserver. Typical tools for that are Apache or Nginx.
  • You'll also need the usual tools to build packages from the AUR.
  • And ruby2.2AUR and ruby2.2-bundlerAUR from the AUR.

Installation

Install diaspora-mysqlAUR or diaspora-postgresqlAUR from the AUR.

Now edit /etc/webapps/diaspora/database.yml and fill out the needed values. Then edit /etc/webapps/diaspora/diaspora.yml and change at least the url setting to the URL your installation will be reachable under (the one served by your reverse proxy). You can change the port the appserver will listen on under the server section. By default Diaspora requires a SSL setup, you can disable that with the require_ssl setting.

Ensure your database is running and then switch to the diaspora user:

$ su diaspora
$ cd

Create the database and initialize the schema:

 bin/bundle exec rake db:create db:schema:load

If the user you specified in the database.yml file can't create databases leave the 'db:create' out and create a database named diaspora_production by hand.

You can now switch back to your regular user and start diaspora systemd service.

The static content your reverse proxy needs to serve will be available under /usr/share/webapps/diaspora/public/

Updating

Updating is very analogous. Obtain the newest version of the package and build it, just like in the installation instructions. Watch for .pacnew files and review the changes. Also read the changelog over at Diaspora. Then again ensure the database is running and switch to the diaspora user:

 $ su diaspora
 $ cd

And update the database schema:

 bin/bundle exec rake db:migrate

Exit and restart diaspora systemd service.

If you notice missing icons or layout issues after restarting the service, switch to the diaspora user again and run:

 bin/bundle exec rake assets:precompile

Once more, exit and restart diaspora systemd service.

Add yourself as an admin

Switch to the diaspora user and start the Rails console:

 su diaspora
 cd
 bin/bundle exec rails console production

Then run the following command, replacing user with your username:

 Role.add_admin User.where(username: "user").first.person

You can exit the Rails console by pressing Ctrl+d.

Troubleshooting

GDM login screen with Diaspora

GDM will insert the user diaspora in its login window because it currently considers the id range 500-1000 as normal users while Arch considers this range for system users as defined in /etc/login.defs. GDM does that probably to keep legacy normal users working. To exclude this user from the login window, add this 'Exclude' line in your /etc/gdm/custom.conf file:

[greeter]
Exclude=diaspora

See also