Feature/docker compose

[AlcibiadesCleinias]

Hey, Arkady

The PR was started from my desire to add a simple compose file, and I am deept in refactoring a bit. Thus:

• add compose file: so db + bot starts with 1 click
• add an entrypoint for a Dockerfile: it checks that Postgres is running (if proper settings in .env)
• rename some constants to uppercase
• move code into src, so we have different layers: layers of orchestrator (docker-compose) with docs, git/github files, useful db scripts (database) then layer with code (i.e. src/)
• move models (tables) in models.py
• add kinda first migration to the app: table initiation (as it should be, coz run primitively SQL query - seems not a good approach to make a 1st migration, i.e. app tables initiation)
• as well to the above: take a note that for migration history and sqlalchemy we should use https://alembic.sqlalchemy.org/

[AlcibiadesCleinias]

If you accept the changes: squash commits pls, ofc

[ArkadyBuryakov]

Base.metadata.create_all() should be used only in cases when you start with new database.

If you have a database with active strategies and different version of models.py - main.py will return Error on this step and won't run.

[AlcibiadesCleinias]

no, it depends on if you create tables yourself with meta that differ from declared in models

[ArkadyBuryakov]

volatabot -> volatobot :)

[AlcibiadesCleinias]

)