Deployster is an extensible resource-centric deployment tool that works by:

• Enabling deployers (eg. You!) declare the desired state of the deployment topology
• It then discovers the topology's current state
• It then attempts to migrate it from the current state to the desired state.

The main differences between Deployster and other, similar, tools (such as Google Deployment Manager, Terraform, and others) are:

• Docker-first philosophy: resource types (eg. VMs, IP-addresses, disks, etc) are written as Docker images, allowing them to be reused in any deployment, on any platform.

• Highly extensible: since resource implementations are merely Docker images - you can create new resource types by creating your own Docker images, using any technology you want. Want to create a new resource that represents a GitHub repository using Ruby? Done. Just implement a new Docker image and write your source code in Ruby inside the image, then use that resource in any Deployster manifest. The Docker image name & tag represent the resource type.

• Stateless: in contrast to similar tools, Deployster will never store your topology state (locally or remotely) which enables your to also work on your infrastructure & deployments manually or in other tools, side-by-side with Deployster. While we are aware that this might incurr a performance penalty at times (for state discovery) we believe this is preferrable to a wrong state discovery.

• Reproducible: deployments are meant to be idempotent, such that running the same deployment multiple times should yield the same result as running it just once, assuming that nothing else modified the state.

The quick start page will get you up & running in 10 minutes. For a more in-depth overview of Deployster, head over to the overview page to learn more about the core concepts in Deployster.

Deployster is distributed as a Docker image available for running on your machine or servers. Since the image requires a certain set of Docker flags, a simple bash script is provided which makes running Deployster a breeze. Here's how:

curl -sSL -O "https://raw.githubusercontent.com/kfirz/deployster/master/deployster.sh"
./deployster.sh --var my_var="some-value" \
                --var another="some-value" \
                --var-file ./my-variables-file.yaml \
                ./manifest1.yaml ./manifest2.yaml

Here's the full run-down of command-line flags available:

[arik@arik ~]$ curl -sSL -O "https://raw.githubusercontent.com/kfirz/deployster/master/deployster.sh" && chmod +x ./deployster.sh
[arik@arik ~]$ ./deployster.sh --help

✔ Deployster v18.0.1

      😄 Deploy with pleasure!
      
usage: deployster.py [-h] [-c {NO,ONCE,RESOURCE,ACTION}] [--var NAME=VALUE]
                     [--var-file FILE] [-p] [-v]
                     manifests [manifests ...]

Deployment automation tool, v18.0.1.

positional arguments:
  manifests             the deployment manifest to execute.

optional arguments:
  -h, --help            show this help message and exit
  -c {NO,ONCE,RESOURCE,ACTION}, --confirm {NO,ONCE,RESOURCE,ACTION}
                        confirmation mode
  --var NAME=VALUE      makes the given variable available to the deployment
                        manifest
  --var-file FILE       makes the variables in the given file available to the
                        deployment manifest
  -v, --verbose         increase verbosity

Deployster was written by Arik Kfir while working @ Infolinks, as a means to improve our deployment process.