Files

Olivier Lambert 58465a80ec Update manual_installation.md

2015-03-09 14:13:08 +01:00

3.6 KiB

Raw Blame History

Manual installation

This installation is validated against a fresh Debian 7 (Wheezy) 64 bits. It should be almost the same on others dpkg systems. For RPMs based OS, it should be close, because most of our dependencies came from NPM and not the OS itself.

FreeBSD user? Check our dedicated page for this.

As you may have seen, in other parts of the documentation, XO is composed of two parts: XO-Server and XO-Web. They can be installed separately, even on different machines, but for the sake of simplicity we will set them up together.

Packages and Pre-requisites

NodeJS

XO needs Node.js. You can install it:

by following this procedure.
on Wheezy, the build from source was tested and working well.
by using n, documented just below.

We'll use n because it's powerful and flexible. First, you need curl. Then, install it as root:

curl -o /usr/local/bin/n https://raw.githubusercontent.com/visionmedia/n/master/bin/n
chmod +x /usr/local/bin/n
n stable

We'll consider at this point that you've got a working node on your box. E.g:

$ node -v
v0.10.36

Packages

apt-get install build-essential redis-server libpng-dev git python-minimal

Fetching the Code

You may either download them here and here or use git with these repositories from http://github.com/vatesfr/xo-server and http://github.com/vatesfr/xo-web:

git clone http://github.com/vatesfr/xo-server
git clone http://github.com/vatesfr/xo-web

Installing dependencies

XO-Server

Once you have it, you can use npm to install the other dependencies: go into XO-Server directory and launch the following command:

npm install

Then, you have to create a config file for XO-Server:

cp sample.config.yaml .xo-server.yaml

Edit it to have the right path to deliver XO-Web, because XO-Server embeds an HTTP server (we assume that XO-Server and XO-Web are on the same directory). It's near the end of the file:

  mounts:
    '/':
      - '../xo-web/dist/'

WARNING: YAML is very strict with indentation: use spaces for it, not tabs.

In this config file, you can also change default ports (80 and 443) for XO-Server.

You can try to start XO-Server to see if it works. You should have something like that:

$ npm start
WebServer listening on 0.0.0.0:80
[INFO] Default user: "admin@admin.net" with password "admin"

XO-Web

First, we'll also install dependencies:

$ npm install

You can now install bower dependencies and build the application:

$ npm run build

Running XO

The sole part you have to launch is XO-Server which is quite easy to do, just launch the xo-server script, which is in the root of XO-Server's directory':

$ npm start

That's it! Go on your browser to the XO-Server IP address, and it works! :)

Misc

You can also consider using forever to have always the process running.

$ npm install -g forever
$ forever start bin/xo-server

Our stable branch is "master" and the beta branch is "next-release". You can change it if you want to test our latest features (on both XO-Server and XO-Web, do NOT mix them):

$ git checkout next-release

If you want to update your current version, do this on both repositories:

$ git pull --ff-only
$ npm install

And this in XO-Web:

$ npm run build

3.6 KiB Raw Blame History