An uptime page to check all of my personal projects, with e-mail notifications when offiline
An uptime page to check all of my personal projects, with e-mail notifications when offiline
This project is now fully functional and monitors the uptime of all configured services, including email alerts when something goes offline. It went from basic monitoring setup to a complete working system with automated checks and notifications.
Worked on improving the service status check logic by updating how responses are interpreted. Now, status code 403 is treated as “up” in the monitoring flow, making the health check more accurate for services that block direct access but are still running.
Also did a bigger cleanup and refactor across the codebase: removed unused modules, improved import structure, and updated the overall service checking logic. I also made some adjustments to the package.json configuration to keep the setup cleaner and more consistent (I forgot to run npm init and went straight to the npm install.
Log in to leave a comment
Another project delivered, and this one is really very useful, at least for me.
I made some modifications so that the verification works on Vercel; the free plan doesn’t accept cron jobs.
Log in to leave a comment
Another project delivered, and this one is really very useful, at least for me.
README and final fixes completed
Log in to leave a comment
I finished tidying up a few things and added the projects to be monitored, now I just need to ship it
Log in to leave a comment
did some ui improvments and bug fixes
Log in to leave a comment
Added email notification via node-mailer
Log in to leave a comment
started the dashboard for project managment
Log in to leave a comment
I created a cron job to check the current status of projects based on the time defined during creation. I also removed the placeholder data from the interface.
Log in to leave a comment
Finally got around to refactoring the CSS. It was getting way too large and hard to manage, so I cleaned it up and reorganized everything. Now it’s down from around 700 lines to about 300, which makes it much easier to maintain and work with going forward.
Log in to leave a comment
Worked on setting up the backend by configuring an Express server and getting everything running properly. Also spent some time improving the UI, mainly focusing on layout and general usability. While doing that, I noticed the CSS is getting pretty messy and hard to maintain, so I’m planning to refactor it using Bootstrap to clean things up and reduce the overall complexity.
Log in to leave a comment
UI completed
Log in to leave a comment