This guide is intended to quickly march you through the steps of installing and running stackd.io and its dependencies.
We’re not intending to be complete or provide you with everything needed for a production-ready install,
we may make some assumptions you don’t agree with, and there may be things we missed.
If you feel anything is out of the ordinary, a bit confusing,
or just plain missing, please contact us.

stackd.io needs a relational database to store internal information.
Since it’s built on Django, it inherently supports many different database servers.
It is preferred that you use postgres, as we make use of it’s json field type.
However, you may use a different database like MySQL if you must,
but it is beyond the scope of this guide to install it.
For more information on Django’s database support, see:
https://docs.djangoproject.com/en/1.9/ref/databases/

The OS-specific prep of your choice (below) will walk you through installing postgres.

We recommend that you create a virtualenv to separate your stackd.io dependencies out into a separate environment,
but it is completely optional. The following commands utilize virtualenvwrapper.
If you’d like to use it, it’s documentation is found here: https://virtualenvwrapper.readthedocs.io/en/latest/

Let’s create a virtualenv to install stackd.io into:

mkvirtualenvstackdio

The virtualenv should automatically activate when you create it.
If you exit your current shell and come back later,
you need to activate the virtualenv again.
To do this, virtualenvwrapper gives you the workon command:

If you created a virtualenv, double-check that it is activated or else this
will probably complain that you don’t have permissions to install
(because it’s trying to install into the global python site-packages directory).

We recommend pulling the latest version from pypi with pip, like this:

workonstackdio# Activate the virtualenv if you created one (optional)pipinstallstackdio-server[production,postgres]

After the install, you’ll have a stackdio command available to interact with much of the platform.
First off, we need to configure stackd.io a bit.
The stackdioinit command will prompt you for several pieces of information.
If you followed all steps above verbatim, then all defaults may be accepted,
but if you deviated from the path you will need to provide the following information:

an existing user on the system that will run everything
(it will default to the stackdio user)

an existing location where stackd.io can store its data
(the default is $HOME/.stackdio/storage and will be created for you if permissions allow)

a database URL that points to a running database you have access to
(if you’re using the postgres install from above,
the default postgresql://stackdio:password@localhost:5432/stackdio is appropriate)

stackd.io can easily integrate with an LDAP server.
See our LDAP Guide for more information on configuring stackd.io to work with LDAP.
If you choose to go the LDAP route,
you can skip this entire section because users who successfully authenticate and are members of the right groups via LDAP will automatically be created in stackd.io.

Admin users in stackd.io have less restriction to various pieces of the platform.
For example, only admin users are allowed to create and modify cloud providers and profiles that other users can use to spin up their stacks.

Note

You will need at least one admin user to configure some key areas of the system.

When not using LDAP, the easiest way to create new non-admin users is to use the built-in Django admin interface.
First we need the server to be up and running so keep following the steps below and we’ll come back to adding users later.

For celery and salt-master, we’ll be using supervisord.
The required packages should already be installed,
so we’ll just need to configure supervisor and start the services.

# generate supervisord configuration that controls gunicorn, celery, and salt-master and store it in the .stackdio directory.stackdioconfigsupervisord>~/.stackdio/supervisord.conf# launch supervisord and start the servicessupervisord-c~/.stackdio/supervisord.confsupervisorctl-c~/.stackdio/supervisord.confstartall

At this point, you should have everything configured and running,
so fire up a web browser and point it to your hostname and you should see the stackd.io login page.
If you’re using LDAP, try logging in with a user that is a member of the stackdio-admin and stackdio-user groups,
or login with the admin user you created earlier.

The superuser we created earlier will give us admin access to stackd.io,
however, you probably want at least one non-superuser.
Point your browser to http://<hostname>/__private/admin and use the username and password for the superuser you created earlier.
You should be presented with the Django admin interface.
To create additional users, follow the steps below.

click Users

click Add user in the top right of the page

set the username and password of the user and click save

optionally provide first name, last name, and email address of the user and click save

The newly created users will now have access to stackd.io.
Test this by logging out and signing in with one of the non-admin users.