IMPROVE CI and related docs

- Remove the last remaining parts of travis CI
- Minor improvements

.github/workflows/test.yml

@@ -18,7 +18,10 @@ jobs:
       - name: Install dependencies
         run: sudo ./install_dependencies_ubuntu.sh
 
-      - name: Run tests
+      - name: Run low-level unittests
+        run: python3 -m unittest
+
+      - name: Run high-level tests on example config
         run: sudo ./example-config/run_tests.py
 
 

README.md

@@ -1,8 +1,6 @@
 # Kastenwesen ╰［°‿°］╯
 
-[![Build Status](https://travis-ci.org/fau-fablab/kastenwesen.svg?branch=master)](https://travis-ci.org/fau-fablab/kastenwesen)
-
-A python script for managing multiple docker containers on a server.
+A python script for managing multiple docker containers on a server. Roughly equivalent to a simplified version of docker-compose, plus status monitoring and automatic rebuilds on security updates.
 
 Imagine your server has multiple services that you want to separate and manage using docker.
 
@@ -12,7 +10,7 @@ Imagine your server has multiple services that you want to separate and manage u
 - You still understand what this script is doing, because all executed docker commands are shown in the output. You could always run these yourself if something goes wrong.
 - If there is a security update for a package that some of your containers depend on, simply run ``kastenwesen rebuild --no-cache``, so that docker's cache is not used and the fresh package is downloaded.
 
-Even more is possible: You can use kastenwesen inside a VM, or even on travis.org, to test your server config before it goes live.
+Even more is possible: You can use kastenwesen inside a VM, or even in a CI pipeline, to test your server config before it goes live.
 
 # Testing it inside a vagrant VM
 
@@ -42,7 +40,11 @@ curl localhost
 
 # Continuous integration
 
-For travis-ci, a demo .travis.yml file is provided. You at least want to run `kastenwesen rebuild` in your CI build.
+If you want to check your server config in CI before deploying, you can find some notes in this section.
+
+You at least want to run `kastenwesen rebuild` in your CI build, wait some time (depending on the configured startup gracetime) and then check `kastenwesen status`.
+
+As a starting point for using GitHub actions, see the CI files .github/ in this repository.
 
-Because of docker, the build needs root privilege. If you want to use Vagrant in a custom CI setup or for developer testing to ensure that your config is correct before going into production, a sample Vagrantfile and kastenwesen_vagrant_test_build.py build script are provided.
+Because of docker and of permissions for the status directory /var/lib/kastenwesen, the build needs root privilege. If you want to use Vagrant in a custom CI setup or for developer testing to ensure that your config is correct before going into production, a sample Vagrantfile and kastenwesen_vagrant_test_build.py build script are provided.
 

example-config/kastenwesen_config.py

@@ -6,13 +6,6 @@
 
 disable_auto_upgrade = True
 
-travis = False
-if os.environ.get("TRAVIS"):
-    print("\nHey Travis, nice to see you. I will progress slowly for you, so my tests won't fail.\n")
-    travis = True
-    STARTUP_GRACETIME = 5
-    TCP_TIMEOUT = 20
-    HTTP_TIMEOUT = 30
 
 #########################################
 # my_linux_base                         #

example-config/run_tests.py

@@ -6,12 +6,8 @@
 
 script_dir = os.path.dirname(os.path.realpath(__file__))
 
-EXTRA_SLEEP = 0
-if os.environ.get("TRAVIS"):
-    print("\nOh hi Travis, how are you? I will go slowly on your machines in order to prevent failing tests.\n")
-    travis = True
-    EXTRA_SLEEP = 5
-
+# extra sleep time in seconds. Must be higher than DEFAULT_STARTUP_GRACETIME. Some extra time can be helpful to work around race-condition bugs in the docker daemon.
+EXTRA_SLEEP = 3
 
 def diagnostics():
     # extra diagnostics output at each build step