Suggestion: It would be cool if it could be packaged as a deb package, install itself as a systemd service, and accept a configuration in /etc somewhere.
Adding nohup commands to /etc/rc.local is a little hacky.
Tinystatus: A tiny status page generated by a Python script
11–20 of 52 posts
Re: Tinystatus: A tiny status page generated by a Python script
#12Earlier quoted context omitted.
Why he need screenshot when there's a perfectly good demo?
Assuming this isn't snark - because if I am looking for a tool to do a job, seeing an immediate visual representation of what I am likely to expect is very helpful. I don't want to go through the full installation to view a demo and then immediately realise it was not remotely close to what I was expecting.
I also think a screenshot in a README is very helpful, but do note that the demo requires no install. The linked GitHub repository has a homepage set, and it is https://status.harry.id which I think is pretty obviously a demo just from the URL.
Re: Tinystatus: A tiny status page generated by a Python script
#13[flagged]
Re: Tinystatus: A tiny status page generated by a Python script
#14It 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
> clean, responsive web page Consider adding a screenshot.
Thanks!
Screenshot added.
Re: Tinystatus: A tiny status page generated by a Python script
#15Suggestion: It would be cool if it could be packaged as a deb package, install itself as a systemd service, and accept a configuration in /etc somewhere. Adding nohup commands to /etc/rc.local is a little hacky.
Thank you for the suggestion!
Re: Tinystatus: A tiny status page generated by a Python script
#16[deleted]
Re: Tinystatus: A tiny status page generated by a Python script
#17Why 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.
good question and answer … on a tangent, it makes me wonder if YAMLscript could be used to preload .env values on startup
Re: Tinystatus: A tiny status page generated by a Python script
#18Thank you for sharing this project! This is exactly what I am looking for.
Re: Tinystatus: A tiny status page generated by a Python script
#19Very nice. But for me the Tailscale dashboard fulfills this function, what would make this super usefully for me if it integrated with something like https://ntfy.sh and I could set conditions for notifications.
Re: Tinystatus: A tiny status page generated by a Python script
#20simple and gets the job done. nice.