News for hackers. Stuff that matters.

sionsmith

Re:My bank has an API so I built online banking on Thursday November 26, 2015 @12:20PM (#10633840)
This is exactly what Tink app have done and they have been in operation for the past 3 years. Legally your using public available endpoints so even if they did block your IP's spin that docker image up on a new host ;)
Re:How We Use Docker For Continuous Delivery – Part 2 on Wednesday June 11, 2014 @09:50AM (#7877958)
Again not sure how Contino do it but if your using autoscaling groups the best way todo this is pass in a bootstrap script (shell or ansible) into the group when creating it so that will pull down the correct images if more instances are needed. To give yourself some control, you should probably do what we do - pass a simple wget in which pulls an ansible playbook stored in S3 so we can change version numbers etc without taking down the whole group. I've found there are many ways todo this but keeping things simple helps alot.
Re:How We Use Docker For Continuous Delivery – Part 2 on Wednesday June 11, 2014 @09:44AM (#7877931)
Ok not sure what Contino do, but you want to do something along the lines of the following:

- Build your java / maven projects as normal.

- Use the maven scm / release plugin to publish your artifacts to your internal maven repo (Nexus) we use.

- In your Dockerfile use wget and the Nexus REST api to pull the jar / zip whatever from the Maven repo. (https://maven.java.net/nexus-core-documentation-plugin/core/...)

- Install Docker publish image plugin for Jenkins (https://github.com/jenkinsci/docker-build-publish-plugin/blo...)

- Create a downstream project based on your java / build.

Once all that is set up, every time you do a push / check in a the Docker image in your registry should be update.

Re:How We Use Docker For Continuous Delivery – Part 2 on Wednesday June 11, 2014 @12:05AM (#7876468)
Hey Ben,

Thanks for the updated post. Could you give us a little more information / git gist ;) on how you achieved this: > Docker registry doesn’t inherently support the concept of versioning, so we have to manually add it using the Jenkins version numbers. > shell scripting to ensure that only 3 were kept in place on each deployment,

Did this involve you appending the version numbers to the image tag? We have a pretty similar set up, and something which you might want to look at is the registry being a SPOF, if that is down then none of the new nodes created by the ELB can be provisioned - create an AWS autoscale group of 1 and assign it an elastic IP to ensure if it goes down the kind bots at Amazon will bring another up for you. (Will require some cloud-init scripting)