An open-source scalable personal cloud

Getting started with StackSync!

StackSync Server

StackSync is an Open Source Personal Cloud that takes care of users real needs and provides a cloud storage solution with scalability, openness and security.

First of all, you need to download and install the StackSync Server (together with the database and the messaging middleware), which is the component in charge of managing metadata and guarantee a correct synchronization among all devices.



You need to install RabbitMQ, which will be used to allow communication between the server and clients.


Database initialization

First of all, install PostgreSQL and its contrib package (that contains the UUID module used by the server).

In order to initialize the database we need to create the database and the user and execute the script “setup_db.sql” located in “src/main/resources“.

Once installed, enter in Postgres command line mode:

Execute the commands below to create a user and the database, and enable de UUID extension.

Enter to the database with the user role created. Note that the first parameter is the host, the second is the database name and the last one is the username:

Now run the script.

Execute StackSync Server

Compile or download the latest version of StackSync Server.

Install the package.

The StackSync Server has a dependency with the JSVC library, if you experience any problem while installing run the following command:

Once the server is installed, you must modify the configuration file to connect with the database, the messaging middleware, and OpenStack Swift.

You need to specify a Keystone user capable of creating users and set up ACL on containers on the specific container configured in the file.

The init script assumes that you have a “JAVA_HOME” environment variable set up, if not, it will execute the java located in “/usr/lib/jvm/default-java”. You can change the Java VM by setting up the “JAVA_HOME” environment or by modifying the script in:

Once configured, just run the server.

If something went wrong, you can check the standard and error log files located in:

Next step

Choose what storage back-end you will use.