There was also this guy, don't remember his name, whom you could email your questions/issues etc, reply with great detail and post the discussion on his website for others to learn from. Like a one on one precursor to stackoverflow.
I remember email him and asking about why my photo gallery didn't work when I tried to save the "currently selected image" as a cookie. He replied and explained to me that cookies contain string values and that you can't save a reference to a DOM element as a cookie. So, cookie = document.getElementById('image0') will not work, but cookie = 'image0' will :)
I had very similar concerns when I was building my sideproject.
But I was determined to ship, so once the code was deployable (the bear minimum, nginx with ssl setup) I pushed to my VPS and posted a link on HN. It was late Sunday night, was very tired, but just wanted to get real user feedback. But I also knew the chances of anyone seeing the link and actually giving feedback were slim, so I tried not to worry too much about it. The important bit was taking the first step and shipping something. Everything else follows from that.
So, my advice is to put it out there and invite people that could give you helpful feedback. Avoid toxic communities as that will only add to the stress.
I had a similar need, and after going through the docs for a few existing solutions (grafana, elastic, prometheus, etc) I decided to roll my own.
No db on the receiver and log-based storage on the senders (using standard log rotation to manage size). A systemd service to write to logs, another to read the last value and push to remote if it has changed. Bash all around.
Other than absolutely 0 maintenance required, and just a $5 droplet, the thing I like the most is the dashboard. It just looks like a spreadsheet. A row for each server, a column for each metric. Click on a cell to view charts for that metric. If metrics are failing health checks cell goes orange, or red if critical. Otherwise it's all gray.
So I can have the dashboard open on a screen and just glance at it and know if something is off. I haven't seen anyone else providing such a dashboard, maybe you can give it a go:)
This is an interesting use case. I can definitely see how a colored cell in a grid can serve as a visual indicator to monitor health of infrastructure. Thanks for sharing this.
db. IN A 100.64.123.1 # prod-db-1.
db. IN A 100.64.123.2 # prod-db-2.
db. IN A 100.64.123.3 # prod-db-3.
This is good for service discovery—e.g., you can configure something like RabbitMQ to discover cluster members from an A record—and it's nice for browsers, which will pick one host at random when connecting, which effectively is load balancing.
In a usual setup, the problem is that if a host goes down, clients will still try to reach it because it's still in the DNS record; but with Tailscale, the "DNS" is generated by the local Tailscale daemon on the fly, so you get a live view, and if this was implemented, it would be possible to only return available servers for tag queries.
Not sure if this trick still applies, or if it applies to your printer, but if you wrap the visible part of the cartridge with black tape the printer will think it's full and let you print.
I've been told that I "have a problem for every solution", and I'm OK with that. It's because I tend to look for things in the solutions suggested that either do not solve the problem, are unrelated to the problem, or are obviously (after a bit of mental poking around) problematic themselves. It's sometimes annoying but most times the process leads to simpler, more elegant solutions (less future maintenance, but more upfront mental effort).
Websites are coded in html, styled with css, and made dynamic/interactive with javascript.
When you right click on a Web page, such as the one you are reading now, and select View Source you can see the html, css and javscript that your browser reads in order to display the page.
Anyone can learn about these technologies and a good starting point would be Mozilla Developer Network (MDN for short) where they have all sorts of documentation on how to get started and what is the state of the art.
Of course, there is a lot more to it but if you just copied/pasted some files on a Web server and it worked this is all you need to know for now.
I remember email him and asking about why my photo gallery didn't work when I tried to save the "currently selected image" as a cookie. He replied and explained to me that cookies contain string values and that you can't save a reference to a DOM element as a cookie. So, cookie = document.getElementById('image0') will not work, but cookie = 'image0' will :)