Thanks everyone at Hashicorp! This tool looks awesome. I wish it had been around years ago so I might have a nice version-controlled set of configuration files instead of a bunch of wiki articles and post-it notes ;)

I have a quick question I didn't see covered in the docs. Is there a best practise way to organise Terraform configuration files? Specifically when using it to manage different environments (e.g. staging, prod, qa). I'm thinking of some sort of folder structure like this:

  /\n    production/\n      web.tf\n    staging/\n      web.tf\n    qa/\n      web.tf\n      test-servers.tf\n

\nSo, `terraform apply production` would then plan and apply changes for production servers, `terraform apply staging` the same for staging, etc.

Would be interested to know if you have any thoughts on this, or if there's some sort of paradigm you folks are using internally.

mitchellh

We should've included a roadmap, but Terraform 0.2 will introduce first-class modules and a [basic] package manager. We'll also address environments then.

otterley

Can we please have a non-sucky package manager so I can finally tell developers to do the right thing instead of begging me for Docker?

icebraining

debs built with fpm[1] have been working for me. Unless you need something particularly complex, it should just be a matter of setting up a directory with the right layout and calling fpm with a couple of parameters.

[1] https://github.com/jordansissel/fpm