Implement application superstructure for passing around #20
This should be something like dependency injection thing. It will be passed around in future refactoring steps.
It should contains logging facility, configuration, HTTP server, database connection (without specifics).
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?