Aiden G

This is a project I made to fetch my public repls and determine which have web servers attached. Of those with webservers, it will run a keep-alive pinger to ensure they never go offline. The targeted scripts will be denoted by the keyword "keep-alive" in the repl description.

Note: It only works for named public repls See at: https://replit.com/@chocolatejade42/keepalive

An alternative to uptime robot that keeps my repl servers alive by pinging them every three minutes. It uses Replit's GraphQL API to fetch all my repls, then filters by those with the keyword "keepalive" in their description. It then pings each of those repls periodically to keep them awake.

This allows me to easily enable "always on" by adding a simple keyword to a new repl's description, rather than spend time configuring uptime robot each time I make a new repl. It also allows for the repls to be pinged more frequently than uptime robot's five minute limit.

The logs on the website can be filtered using the "search" query in the URL to filter certain repls, levels, or dates.

Note: Uptime robot will still need to be configured to keep this repl alive, but it's better than having to make a new monitor for every repl! Setting up uptime robot: https://replit.com/talk/ask/Yes-you-can-using-uptimerobot-like-Va/18608/50032

~ @chocolatejade42

keep!!!!alive