Tinystatus: A tiny status page generated by a Python script
https://github.com/harsxv/tinystatusIt generates a simple, responsive static HTML page for those of you running self-hosted services and wanting to share their status page. It checks things like HTTP pages, open ports, or pings IP addresses.
Check the demo here: https://status.harry.id
loading story #41453107
loading story #41458556
loading story #41455595
loading story #41454495
loading story #41458693
Why not put these .env variables inside the checks.yaml config file? What is the advantage of two config files with two separate syntaxes?
The idea is the values in .env files can be configured via environment variables, while checks.yaml is for things that can be hard coded.
In this case it's a bit moot because the yaml file works like a database, but when you deploy this using, say, Docker or k8s, you can use a different method to configure environment variables and skip .env files.
Why can't I change the port of my database server via an environment variable? This would be required for e.g. Nomad support.
If this is a goal, why is it a goal for only half the configuration?
Something I do in my yaml configs is support ${ENV} template variables with the string Template's substitute method using *os.environ.
good question and answer … on a tangent, it makes me wonder if YAMLscript could be used to preload .env values on startup
loading story #41452861
loading story #41458121
loading story #41453909
loading story #41458063
loading story #41455652
loading story #41460332
loading story #41456100
loading story #41454472
loading story #41455150
loading story #41455973
loading story #41454349
loading story #41454157
loading story #41455489
loading story #41457376