An approach to developing simplified API(s) as a boilerplate in Golang leveraging MongoDB and JSON-API.

I have spent the last sixteen months struggling to develop services using Golang in a way that seems successful. Having some measureable amount of success or being successful includes having repeatable steps and a foundation for progress. I have developed, refactored, deleted, and started over more times than I can count and now I am committing myself to going in one direction, forward.

Each major commit or branch of this code will represent some lesson or lessons I am trying to learn. They will likely be formalized into more of an article at some point for me to declare some small amount of victory with this approach, but we shall see.

I continually monitor the progression of great code coming out of my friends and colleagues and I envy their ability to write stuff that doesn't suck. I am absorbing their brans to help my code not suck nearly as bad.

THanks to all of the various make a restful api in golang articles that are all over the interwebs for giving me plenty of information to read.

• json-api - is where I am trying to get the infos for making this not suck entirely.

Merging the branch 'divide' into master to become version 0.0.2 as unofficially official as I can. Basically, I decided to spend some time splitting up the single file api into a few more manageable packages. Not entirely sure they are grouped logically as I still have some Host details in community-api/main.go and such.

• Added 'corsHandler'
• Modify Host data