Bottler (BETA)

Bottler is a collection of tools that aims to help you generate releases, ship them to your servers, install them there, and get them live on production.

What

Several tools that can be used separately:

release: generate tar.gz files with your app and its dependencies (not including the whole erts by now).
ship: ship your generated tar.gz via scp to every server you configure.
install: properly install your shipped release on each of those servers.
restart: fire a quick restart to apply the newly installed release if you are using Harakiri.
deploy: release, ship, install and then restart.
rollback: quick restart on a previous release.

You should have public key ssh access to all servers you intend to work with. Erlang runtime should be installed there too. Everything else, including Elixir itself, is included in the release.

By now it's not able to deal with all the hot code swap bolts, screws and nuts. Someday will be.

Use

Add to your deps like this:

    {:bottler, " >= 0.2.0"}

Or if you want to take a walk on the wild side:

    {:bottler, github: "elpulgardelpanda/bottler"}

On your config:

    config :bottler, :params, [servers: [server1: [ip: "1.1.1.1"],
                                         server2: [ip: "1.1.1.2"]],
                               remote_user: "produser" ]

Then you can use the tasks like mix release. Take a look at the docs for each task with mix help <task>.

Release

Build a release file. Use like mix bottler.release.

prod environment is used by default. Use like MIX_ENV=other_env mix bottler.release to force it to other_env.

Ship

Ship a release file to configured remote servers. Use like mix bottler.ship.

prod environment is used by default. Use like MIX_ENV=other_env mix bottler.ship to force it to other_env.

Install

Install a shipped file on configured remote servers. Use like mix bottler.install.

prod environment is used by default. Use like MIX_ENV=other_env mix bottler.install to force it to other_env.

Restart

Touch tmp/restart on configured remote servers. That expects to have Harakiri or similar software reacting to that. Use like mix bottler.restart.

prod environment is used by default. Use like MIX_ENV=other_env mix bottler.restart to force it to other_env.

Deploy

Build a release file, ship it to remote servers, install it, and restart the app. No hot code swap for now.

Use like mix deploy.

prod environment is used by default. Use like MIX_ENV=other_env mix deploy to force it to other_env.

Rollback

Simply move the current link to the previous release and restart to apply. It's also possible to deploy a previous release, but this is quite faster.

Be careful because the previous release may be different on each server. It's up to you to keep all your servers rollback-able (yeah).

Use like mix bottler.rollback.

prod environment is used by default. Use like MIX_ENV=other_env mix bottler.rollback to force it to other_env.

TODOs

Add more testing
Get it stable on production
Options to filter target servers from command line
Wait until current release is seen running.
Complete README
Rollback to any previous version
Optionally include erts (now we can ship openssl too see here)
Use scalable middleplace to ship releases
Allow hot code swap
Support for hooks
Add tools for docker deploys