Split configuration into Development/Production and, maybe Standalone

[ravenvz]

Right now, to start playing around with local version of the app, quite a few
changes have to be made. For example, here are steps I had to do:

• It does not make much sense for me to use PostgreSQL on local machine,
  so I had to alter requirements.txt to not include psycopg2 adapter;
• I had to change App config to use sqlite db;
• A had to use a hack to bypass GitHub authorization.

Steps like these are tedious to do by hand and should be handled by configuration files.
I think, that separation of configuration would help new contributors to get started more quickly.

This issue intersects with #10, as it would probably require separate configuration anyway.
If this proposal is accepted, I could work on it. Please let me know if it makes sense.

[eleweek]

This totally makes sense, I'll start working on this today.

[eleweek]

Hey, I added some work to address these issues, and I updated README file to include basic installation guide. Could you please check it?

[ravenvz]

Great! I have checked it and it looks like everything is working fine (I only checked standalone version). I added some additional clarifications to README.md.

[ravenvz]

I would also like to try to move configuration part from app.py file to separate file, something along the lines of Development/Production section of flask documentation

http://flask.pocoo.org/docs/0.10/config/

Now, I would like to do this for myself in any case to get more familiar with Flask framework in the process, but if you are interested, I can make a PR if I like the result.

[eleweek]

Thanks, I accepted the PR. As for configuration management, is there any advantage over using .env + foreman?

[ravenvz]

Well, I had studied foreman more closely since the time from my last post (never used it before), and it turns out that there will probably be no advantage at all, so - never mind!

I guess that issue is resolved then?