Files
@ 8277b8bac851
Branch filter:
Location: C3L-NOC/tls-expiry-tracker/README.md - annotation
8277b8bac851
641 B
text/markdown
docs: remove done frontend plans
af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 af8faf2c7104 | # X days since last outage caused by TLS expiry
How often does your infrastructure break because you forgot to automate TLS renewal, or because it broke?
Find out by rolling out this tool with the domains and services!
## Plans
### Backend
- Python script for backend
- check each domain's tls cert using [`ssl` library](https://docs.python.org/3/library/ssl.html)
- use file(s) to store:
- domains
- expiry status *per* domain
- log of outages
- cronjob at the start (every 1-5 minutes)
### Frontend
- Javascript
- fetch generated JSON from "backend" (web server)
- every X seconds
- re-render the counter every second
|