Jeffrey Devloo

Must have been bad luck. The token that is provided stays for 24hours. A decision should be made whether - our API should automatically refresh the tokens in the client...

Things to be done: **Server side:** - Add a new type of token which is persistent (should never be removed automatically): the refreshing token (4h with refactoring other token logic)...

It could be that the exit code is actually 0, a clean shutdown. We should set the restart to always instead of on failure to restart in all cases

While testing I've noticed some behavior that might indicate this issue: - Bring watcher down - Brings down web-api & workers - web-api in deactivating state & workers in inactive...

# Test report ## Setup The testing setup is as follows: **test_main.service**: a simple overlooking service which can be bound onto by others (mimicks the watcher) ``` [Unit] Description=Application Control...

Both for the Nuvolat setup as for our testing preparation this can be handy. Nuvolat is currently preallocating x amount of disks, would be nice to do without a for...