Question: What's the reason for not using a web framework?

[abraithwaite]

Simply out of curiosity, what was the reason you chose not to go with one of the golang web frameworks?

[bradrydzewski]

Hi Alan, I'll write a blog post about the topic of web development with Go, and some of the choices we made. We did use a number of tools to simplify development:

• bmizerany/pat for routing
• dchest/authcookie for secure cookies
• dchest/passwordreset for password reset
• russross/meddler for database mapping

Were there any specific frameworks you were wondering about?

[abraithwaite]

Ah, I didn't see you were using pat. It looks like the combination of those packages is a pretty comprehensive solution. Although, the one thing that stuck out to me was writing raw SQL. I'm not even sure if there are any good ORM framework for golang yet, but that's primarily what I value in a framework.

I haven't written anything in golang personally, but after hearing about Docker I had essentially the same idea for building a application that tests using Docker containers.

The killer feature that I want it for is committing the container image to an index after testing is completed, allowing for developers to check out the result locally and debug the result.

Anyways, my advice to you is if you want to have lots of good contributions then write a design document describing your architecture and libraries that you use so that new contributors can get started quickly.

I really like what you're doing here and I hope I can find time to contribute something. You can count on me watching this and trying it out for myself.

[bradrydzewski]

Yes, I'll definitely write some documentation on the architecture and project organization

there are two main orms in go:

• https://github.com/coopernurse/gorp
• https://github.com/jinzhu/gorm

gorp doesn't support joins so you'd end up writing your own SQL anyway. gorm was brand new when we started building Drone and we wanted something stable. It may be worth another look.

meddler is nice because it generates the SQL for INSERT and UPDATE, and handles column mapping for our SELECT statements. So we only had to write SELECT statements, which wasn't too painful. I think what I really miss is a good migration utility provided by most ORMs

support for publishing Docker images should land this month, so stay tuned!