[johnb]

I've been using wercker to test and auto deploy a few sideproject go apps and the process has been really smooth. I'm about to switch one over to their new ssh deploy stuff and will write a blog post about it.

Using them as a plain CI/badge system for libraries is really nice too: I'm using them on https://github.com/joho/godotenv for that and have been really happy with that.

Two thumbs up from me for the service all round.

[slogsdon]

I just finished up configuring one of my apps with their ssh deploy step. The whole process of defining build and deploy on green steps makes their service easy and worthwhile. I'm excited to see what they have in store for the future.

To add, Wercker's customer service is pretty awesome as well. One of their guys forked my app and submitted the necessary changes to get it to properly build when I was unable to do so myself. I think this dedication towards making sure the customers enjoy their service is going to help build their customer base.

[chourobin]

How does wercker compare to Ansible or Chef?

Btw, great work on Goodfilms.

[miesie]

Ansible and Chef are tools that provision your servers. Wercker is a continuous delivery platform that tests, builds and deploys your applications. All of this packaged in an easy to use interface where you can also collaborate with others.

You can leverage tools such as Ansible, Puppet and Chef on wercker to create the environment (a wercker box) that mimics your production system, again to build, test and deploy your app, keeping dev/prod parity in true 12factor fashion:

http://12factor.net/dev-prod-parity

We've written up a post on provisioning wercker boxes which you can deploy to the wercker directory (http://app.wercker.com/#explore) here:

http://blog.wercker.com/2013/08/21/Overview-of-provisioning-...

Feel free to contact me if you have any questions!

cheers