3 ms·
I've been working on creating a platform for a non profit to get veterans coding (http://operationcode.org/ http://operationcode.org/). We're a slack based comm
by rickr 10y ago
I've been working on creating a platform for a non profit to get veterans coding (http://operationcode.org/ http://operationcode.org/). We're a slack based community and have been rolling out some home grown slack bots and we currently have a rails app hosted on heroku. Managing and keeping track of the different apps was getting unwieldy so in an effort to consolidate our apps and reduce costs I evaluated a few different options. I ended up going with rancher and after working with it a bit I'm pretty happy.
I have github hooked up to travis. When a new PR (or commit) is pushed travis shoves the app into its container, and runs the test suite inside the container.
If that passes AND the branch is master we push the image to docker hub. As of now we manually update the app inside of rancher but I think automating that will be a simple API call. Once we get more stable I'll be investigating that.
I still haven't quite figured out secret management but outside of that and a tiny learning curve it's been pretty smooth sailing.
An example travis config:
https://github.com/OperationCode/operationcode_bot/blob/master/.travis.yml https://github.com/OperationCode/operationcode_bot/blob/mast...
- thinkdevcode 10y agoOfftopic, but that's a really awesome idea for our veterans. Thanks for working on it!
- spudfkc 10y agoI do something very similar but with GitHub and Teamcity. Automating the upgrades (i.e. redeploys) in Rancher is pretty straight forward - their API is super easy to use. I ended up writing a simple tool in mostly Bash to handle it, and threw it in a Docker container to run on Teamcity.