bar-tender

We have a small vCenter lab. It would be helpful to have a check out system for the virtual resources. Just the basics so users can see what resources are available, check them out, and release them. As a bonus it would be very useful if our automated tests could do the same.

So what we need is:

• user registration

• user authentication

• equipment CRUD

• equipment reservation

• web interface

• scripting interface

• simple reports

• use RESTful techniques

We like to code name our product development sprints after bars, so let’s call this project “bar-tender”.

Journal

The chronicles of developing bar-tender are in the journal directory. I tried to include every step, but did skip some of my head scratching, research, trail and errors (emphasis on the later) that went into the development.

Thank You!

A big thank you to:

• Yorrick Peterse for Ramaze

• Everyone who has contributed to Ramaze

• The Ramaze Google Group for all their help

References

• www.ramaze.net

• gembundler.com/

• github.com/rack/rack

• mjijackson.com/rack-accept/

• github.com/brynary/rack-test

• github.com/intridea/omniauth

• rspec.info/

• cukes.info/

• github.com/colszowka/simplecov

• sequel.rubyforge.org

• www.sqlite.org/

• www.postgresql.org/

• json.rubyforge.org/

• pragprog.com/book/achbd/the-rspec-book