Remove dirty hax, fix dependencies

[SuperPrower]

Hi. Several steps were preventing me from running a server. I attempted to fix them in this commit, including fixing missing and broken requirements and removing need for meddling with system environment.

[SuperPrower]

Noticed I made a small mistake: folder name in run.sh script is not required. I'll fix this plus few more things.

[SuperPrower]

Should be OK to go now. Works out of the box, without meddling with .bashrc and stuff.

[iharshulhan]

Environment variables are used to separate production environment and local for testing. It uses different servers and protocols. Removing them is not appropriate.

The issue with requirements.txt was correct 👍

[iharshulhan]

This is already achieved in app.py

[iharshulhan]

This script may be executed from other folder and environment variable will wrong in that case

[SuperPrower]

1. You don't have to set environmental variables in .bashrc for them to work. You can set them in flask.sh script. Separating development and deployment versions can and should be done using Flaks Configuration, and even then, you can use isolated variable in shell script as opposed to global one in .bashrc.
2. The purpose of serv.py is to avoid adding your directories to global python PATH. With this, your application will see both api and db directories just like that, because they are in same directory as serv.py.
3. dirname command solves the issue - it returns the location of the script, although relative. _BACKEND_PATH would be set appropriately using it.

[iharshulhan]

I agree that you don't have to add them to bashrc. The line is wrong, one just needs to set environment variables in a convenient way. Flask configuration won't do, as WGSI server with SSL encryption is used for production version, which requires different code execution controlled by environment variable. Anyway, there is already config.ini which stores necessary variables and config_production.ini on production server, but in order to share the same code both on local and production machines, environment variables were used to load a right version of configuration and start a different server. If you can add your flask.sh script to deployment script and change the message, I would gladly accept the pull request.

I see the point of serv.py, but to make it more generic, please, create a function in app.py responsible for starting the application with all appropriate logic. Then you can call that function in serv.py. I would still keep a line with PYTHONPATH, but in that case you can add a comment that it is optional.