TODO

Timing:
15:40 - 15:55 - Investigate: what will be needed when doing facthub


Tasks:
1. Instead of machines/<service> do:
- machines/vagrant/<service>
- machines/docker/docker-compose.yml with build commands
- user can choose between provisioning local boxes using dockerfiles or ansible
1. Deploy with Terraform best-practices without atlas.
- change deployment to be done in eu-west-2 (by using variables)
- make use of profiles
- automate cert and key generation
- initialize python classes properly
    - provider (aws/ovh/azure)
    - env
    - provisioner (ansible/puppet/chef/saltstack)
    - infrastructure manager (terraform/cloudformation)
    - vm manager (vagrant/docker)
    - local config file (with secret)
    - service (with git)
    - store (remote or local by using infra provider)
    - cloud store
    - environment store
    - image builder (packer/local-aws-builder)
- if wanting to just create specific part of infra run terraform file as module with vars from specific directory
4. Commands available in cloud repo (local docker/vagrant and aws with terraform and ansible/cloudformation)
    - infrav (--environment)
        - create
        - destroy
        - start
        - stop
    - provision (--tag, --service, --environment)
    - build (--service, --build-type, --push-local, --push-remote)
    - pull ()
    - test (--service, --type=<integration|unit|acceptance|behavioural>)
- commands available in workspace/<service-name> dir
    - same as with cloud repo, but with --service flag already filled
- create mkitdevelopment-company:
    - mkitdevelopment service (using wagtail cms with semantic-ui)
    - frameworks service (hello world page served by framework)
        - use one from each language https://en.wikipedia.org/wiki/Comparison_of_web_frameworks
        - or this https://github.com/showcases/web-application-frameworks
    - services:
        - solr
        - RabbitMQ
        - Tomcat
        - Neo4j
        - codecata pythone exercices