If you have questions about our hosting, please use the Hosting Support category.
I admit to being unclear, so if I erred there, my apologies.
Asking how to skirt our limits is not “general chit chat”.
I believe you have mistaken my intentions, here. I am not trying to skirt the limits, but rather to engineer my site to gracefully degrade if I am approaching the hits limit for the day, as to avoid being shut down randomly for 24 hours. I am uncertain if what caused the shutdown I just endured was a site error on my part or a DOS attack, so having the site monitor its own vitals would be a useful feature to help avoid issues going forward.
I moved your topic for now, but please pay more attention next time.
As for your question itself, no you cannot check your site’s resource programmatically.
So a graceful degradation model will not work. Thank you for the reply. I will have to think of another way to manage things.
After all, we want you to stay within the limits, not to do your best to use as much server power as possible just before getting suspended.
I respect that point of view. Minimizing server load while maximizing site usefulness is the goal, here. In the case of my site, it is just a custom-created wiki for my worldbuilding, so it shouldn’t be anywhere near generating that many hits in a day under normal circumstances. I would host it myself off a raspberry pi on my home network if services that convert my dynamic DNS into a static one were still free to use, but as far as I can tell that is not a viable option in the current environment.
If you’re worried about images generating too many hits, you could also offload the images to an image hosting service ahead of time. That way, you can skip the conditional checks.
An interesting idea, there. I will definitely consider finding some other hosting service for that media. I would do the same thing with the other likely cause of hit generation (the articles directory that the wiki uses to build the displayed content), but cross-domain fetches of text files are a security issue that most browsers would block out of hand.
Thank you again for your time.