- Clean installation of Ubuntu host
- Internet connection
From within the line-docker-counter directory:
chmod +x install.sh
sudo install.sh
sudo ./test_no_coverage.sh
curl -s http://localhost/counter/?to=1000
db/db_creation.sql
is added for reference purposes only, otherwise the database is to be used "as is".
- Using third party image to run nginx proxy server
- Even though the counters are not physically deleted from the database upon app server shutdown, the functionality is fully preserved
- Tests are submitted to coveralls from the docker container inside of the travis container. The choice to use the docker inside travis is due to design, as we might want to have some test that require cross container testing. The warnings/errors coming up from within the travis builds are expected and not to be treated as errors, as the tests are run from within the docker and not the travis itself. The coverage shows lower than it actually is(close to 100%) due to testing functions directly, and not through testing Flask, I assume.