Currently, it has none which results in logspam on start like Could not load the spec: Error: ENOENT: no such file or directory, open '/srv/deployment/tilerator/deploy-cache/revs/b50104637b2854db66f62c6ef157aa7a0be08fc7/src/spec.yaml'
While Tilerator has no publicly available HTTP interfaces, does it make sense to add a check to e.g. verify that tile generation still works?
While Tilerator has no publicly available HTTP interfaces, does it make sense to add a check to e.g. verify that tile generation still works?
This is a great idea! We could then also add checks to the deployment process so that on every deploy tile generation would be checked on the target nodes before the new version is activated.
Moving off the sprint board - the Discovery team won't be able to do this work at this time.