Skip to content

Instantly share code, notes, and snippets.

@jpic
Created September 29, 2018 04:16
Show Gist options
  • Save jpic/20edf8b1877a0e8fac6844e62682e98c to your computer and use it in GitHub Desktop.
Save jpic/20edf8b1877a0e8fac6844e62682e98c to your computer and use it in GitHub Desktop.
Help displays without argument for the playlabs command
29/09 2018 06:13:36 jpic@jpic ~/src/playlabs/playlabs/inventory_template (master)
$ playlabs
Playlabs: the obscene ansible distribution.
Init your ssh user with your key and secure sshd and passwordless sudo:
playlabs init root@1.2.3.4
# all options are ansible options are proxied
playlabs init @somehost --ask-become-pass
Now your user can install roles:
playlabs install docker,firewall,nginx @somehost
And deploy a project, examples:
playlabs @somehost deploy image=betagouv/mrs:master
playlabs @somehost deploy
image=betagouv/mrs:master
plugins=postgres,django,uwsgi
backup_password=foo
prefix=ybs
instance=hack
env.SECRET_KEY=itsnotasecret
playlabs @somehost deploy
prefix=testenv
instance=$CI_BRANCH
image=$CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
If you have that work, creating an inventory is the way to move on, wether you
want to version configuration, add a deploy user for your CI, configure a
secret backup password, add ssh-keys ...:
playlabs scaffold ./your-inventory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment