Deploy Frameworks

You have a number of options when installing Diaspora on Ubuntu - these include doing so manually or installing through Cloud 66 EasyDeploy.

Depending on your configuration, a manual installation of Diaspora can take up to a few days. Deploying through Cloud 66 on the other hand takes up to an hour for the initial deploy, and up to five minutes for subsequent deployments.

3. Next, choose where you’d like to deploy Diaspora, the region and server size. You can also choose if you’d like to deploy to separate web and database servers.

4. Once you’re happy with your configuration, simply click ‘deploy’, and sit back and relax while we deploy Diaspora for you.

Option 2: Manual Installation

1. Requirements

Hardware

For running an average-sized pod, your server should have at the very least 512MB of RAM (+1GB swap space) and a decent multi-core CPU. The amount of hard disk space required largely depends on how many images you expect your users to upload. If you plan to run the database server on the same host you should allow for at least double the amount of RAM and disk space.

If you installed RVM via the package manager, we recommend to remove it. See this StackOverflow answer for some tips on how to do that and then continue with the installation instructions below.

RVM

We recommend using Ruby Version Manager it will ensure you’re always on the currently recommended Ruby version and cleanly separate your Diaspora installation from all other Ruby applications on your machine. If you opt for not using it ensure your Ruby version is at least 1.9.2-p320, prior versions are incompatible. Be aware that his version is not maintained with security updates from the Ruby core team anymore. We do not support Ruby 2.0 yet. We currently recommend using 1.9.3-p448.

Install RVM

As the user you want to run Diaspora under, that is not as root run:

curl -L dspr.tk/1t | bash

and follow the instructions.

Set up RVM

Ensure the following line is in your ~/.bashrc:

[[ -s “~/.rvm/scripts/rvm” ]] && source “~/.rvm/scripts/rvm”

Now close all open terminals and open a new one!

If you don’t have sudo installed or your current user doesn’t have the privileges to execute it, run:

rvm autolibs read-only

Then closely watch the output of the next step for something like “Missing required packages:”. If it appears, hit Ctrl+C and install all the packages listed there.

environment.certificate_authorities: You have to set this, one of the examples should fit. If the file in the example doesn’t exist you’re missing a package, in most cases it’s named ca-certificates.

server.rails_environment: You must set this to production. The server section is read by ./script/server and most alternative startup methods to setup the correct environment.

environment.require_ssl: If for some reason you can’t run your pod on HTTPS (we highly encourage you to do it!), set this to false to prevent a redirect from http:// to https://

Reverse proxy

You most likely have already a webserver running on port 80 (http) and 443 (https). It also should serve Diasporas static content and forward all other requests to Diaspora. Here are some example configurations to achieve that: