Improve Deploy Process

[artasparks]

Everyone would really like to improve the deploy process. Currently, the process looks like:

• ssh into the machine.
• apt install docker/docker machine
• DL the container[s] and run them.

This process could probably be improved. @duckpunch mentioned using Ansible script to provision the machine. A middle ground might be using Ansible with docker: https://www.ansible.com/docker

I would also personally love it if Green travis builds automatically initiated deploy process. This isn't trivial, however, and would doubtless require the building of a custom travis script and adding encrypted credentials to the travis script.

[brilee]

It's a bit worse than this actually; docker-compose build is being executed on the deploy target machine, so the container built by the dev on his local machine, and the container built on the deploy target machine are only theoretically the same. (I did this just to see if I could get things up and running; hadn't had time to look further into it.) I think fixing this is as simple as registering an account on the public Docker registry and uploading/downloading from there.

[artasparks]

Ah, I see. It should be a relatively straight forward to fix that.

[duckpunch]

Green travis builds automatically initiated deploy process

How well is Travis built for CD? Have you used it? How deep was your usage of it?

Other (open source) options include:

• Concourse
  • Pretty well regarded, inspired by go.cd below
  • Comparison with other CD options - go.cd, travis, jenkins are in there.
• go.cd - somehow seems appropriate for this project?
• Jenkins - I hear its garbage but I haven't used 2.0 - the version that has the CD features.

[artasparks]

How well is Travis built for CD? Have you used it? How deep was your usage of it?

I haven't used it, but I've been doing some reading here and there on it over the last couple of days. I'm totally open to ideas (thanks for the links!) From looking at the other options mentioned, it looks like most of these would require setting up a separate deployment server, correct?

[duckpunch]

Yep. It would make CI more complicated for the various CD features (push button deploys, pipelines, logs, access controls, etc)

[artasparks]

Note that images are now automatically built and pushed when changes are merged into the 'release' branch. Then, these images automatically get pushed to the USGO docker hub repo: https://hub.docker.com/u/usgo

[artasparks]

Still to do:

• Tag the images in an intelligent way
• Automatically check for new release images and redeploy them
• Integrate with docker compose

[artasparks]

Ok, tagging is done to my satisfaction for now. Still have:

• Automatically check for new release images and redeploy them
• Integrate with docker compose