Future Meeting - General (10/11/13)
Closed this issue · 2 comments
Time: 5pm CEST
Participants: Mark Hendrickson, Jack Pearkes, Ryan Barrett
Communication: Google Hangout (https://plus.google.com/hangouts/_/b97ea47eb2867afa1daba9f169e7c35e587ed3e6)
Bumped this to next week, and am going to throw down some stuff hopefully I'll be able to talk about, but also just writing it down so everyone is aware of what's going on.
vm-templates
I set up an initial vm-templates repository. This currently contains a Packer template and some provisioning scripts for a simple local VM for working with a Python focused API. This will be useful for all the planned Python API's, and can be extended to handle stuff like RabbitMQ or Redis or whatnot if need be.
The benefit to doing VM development is that development and production environments get really close to parity, and it also makes set-up for a multi-dev project just a few commands and installed dependencies that many people already have.
To do API development, for example, people will only need to install Vagrant, VMware or Virtualbox and then run:
$ vagrant up
That's all. They can then SSH into the machine and run tests, the development server, etc.
Additionally, it's great for a service-oriented workflow that involves potentially multiple services talking to each other over the network.
Finally – using Packer, adding different "builders" is trivial. A builder could be on Amazon or OpenStack, etc., and lets us build images (like an AMI) for those providers. All of those provisioning scripts and configuration will be identical, minus one or two environment things, in development and production.
It's not likely everyone will need to use Packer. I'll primarily build Vagrant boxes for development which anyone will be able to pull down off of S3 or something and immediately start hacking on the actual code rather then fiddling around with their environment. Vagrant automates this process.
accounts
I stubbed out and wrote a bunch of docs for the initial accounts API. This is definitely a first pass and I'll be working on getting this operational over the next few days. It probably doesn't even boot the web app right now.
More repos...
I'm going to do what I did with accounts for the other services we need to get that initial product out there as we discussed in #6 and #2.
That's it for all that stuff. Feel free to swing questions or suggestions at me – but otherwise I will forge ahead. We can talk live about this at the end of the week, and Mark and I are actually going to be in person all of this week so I'll do my best to indoctrinate him. ;)
We've bumped this subsequent meeting off more than a week to put our heads down coding. Jack, how do you want to do a follow up to the stuff you've posted here?