Files changed (1)
- Ignore whitespace
+I am proud to present Kodig, my first Django app. Developing it has been pretty fun. It underwent a lot of changes through development before ending up the way it is now. This post will be a brief walkthrough of the development of Kodig.
+I wanted a place to write quick notes which don't really fit in this blog. I like to keep this blog strictly development related. I also didn't want the hassle of setting up a separate Wordpress/Tumblr/etc. Google+ would've been perfect, but sadly it doesn't support Markdown. So I decided to build my own.
+The original idea for Kodig came from my brother. His idea wasn't very well defined. I think he wanted something similar to email but with the capability of sharing the conversation with anyone or making it public and with some social integration.
+Meanwhile, I've had my own ideas about a public "diary" of sort, where everyone can post public or private entries without worrying about their identity.
+I've been learning Django for a long time now but I've never been able to finish anything with it, so this is pretty exciting for me.
+I recently used Flask to build my Reddit based project, r.doqdoq. Now that I think about it, Flask would've been a better choice of framework for this project since it's fairly simple and doesn't really use most of Django offers. But it's too late for that now. I'm still glad I went with it.
+- **Easy deployment via ep.io** - ep.io was pleasantly easy to deploy to. Sadly I'm only using a free instance at the moment, so I'll have to look into more permanent hosting options once the site starts using up its alotted resources.
+- **South** - Being able to modify your models while the app is deployed is awesome. Although I did break my database while migrating on ep.io, fortunately no important posts were lost (just a bunch of test posts).
+- **Templates** - Django's templating system isn't really too bad, but having tried Jinja with Flask, I can't help but feel that it is a bit lacking.