- install python
- install flipside-platform
See all available templates
flipside-template list
Initializes the flipside app
flipside-init <app_name> <template_name>
Writes config into .flipside/
To build locally:
flipside-build
Uploads the app into the master:
flipside-publish --target=[aws|vagrant]
To bootstrap a machine (later you can provision salt on it):
flipside-bootstrap --target=[aws|vagrant] --keyname=<keyname>
When target is aws:
- the newly created key is stored under
.secretsdir - the master configuration is stored in
.flipside-platform.yaml
Installs salt and ancillary packages in the master machine
flipside-provision --target=[aws|vagrant]
Salt version defaults to stable latest
Standalone (masterless) mode can be set using the --standalone option
Push salt states and pillars into the master
flipside-configure --target=[aws|vagrant]
KNOWN ISSUES:
The following salt config files are global and shared between all apps:
.flipside/salt/config.yaml.flipside/salt/state/top.sls.flipside/salt/pillar/top.sls
Every flipside-configure overwrites what was written by the previous one. To
overcome this issue, just make sure all apps in a single master have the same
files
Multiple app instances of the same templates are not supported on a single master. Fixing this is trivial: app put their state files in separate paths and app pillars and other config have to be prefixed by {{ app_name }}
Deploy an application
flipside-deploy --target=[aws|vagrant]
KNOWN ISSUES: deploys all apps together
flipside-ssh --target=[aws|vagrant]