Installation

This page contains outdated information!! (30-10-2014)

---

This installation guide is based on CentOS 6.5 minimal iso. All the current installation scripts have been integrated into a couple of scripts in the install/ directory of invenio-scripts.

NOTE: the development effort is done on the master branch. Old code is branched from master to b2share-old for historical purposes.

Changelog

1. As of 2014-08-04 b2share-next is merged into master;

Structure overview

Two repositories are required to install the B2SHARE service:

1. b2share (invenio, b2share module, minor invenio tweaks);
2. invenio-scripts (install scripts, Vagrantfile).

B2share contains all the functional source-code, whereas invenio-scripts is targeted to handle installations for deployment and development.

Installation

To install the software stack complete this README.md. As the README describes there are two setups possible: development and deployment.

NOTE: Shared Folder

Development requires your host system to checkout/ clone both b2share and invenio-scripts repositories in a single directory, as described below.

NOTE: vagrant will throw an error if no b2share folder is present!

$ ls /path/to/your/repositories/
  b2share     invenio-scripts     ...

Vagrant will mount the b2share (on your HOST machine) via shared_folder into the same directory as the deployment script will clone the latest version of master.

NOTE: Dangling VMs

Vagrant (invenio-scripts/install/Vagrantfile) describes two configuration: dev -> development, and default -> deployment. If the name default is changed, the already installed VM will be dangling. Vagrant will not have control over it anymore. If it were to happen, you should either kill the VM manually, or reconfigure the Vagrantfile so it recognises default.

NOTE: Running both VMs

Both VM configs forward the same ports, so only one VM can be active at a given time.