seansaito / Roster

A Tor project that awards points and badges to relay operators based on the performance of their families
5 stars 1 forks source link

Occassional HTTP 500 errors #7

Closed virgil closed 8 years ago

virgil commented 8 years ago

Maybe about 10% of the time I click to a tor-roster.org URL I get an Error 500. And when I don't get an Error 500 it seems to take a while for it to load? What's the problem? I presume it's some sort of backend thing. Should Roster run its own instance of Onionoo? Alternatively, does some kind of caching need to be implemented? I'm happy to pay for caching via Fastly/CloudFlare.

seansaito commented 8 years ago

Let me play with Apache caching

virgil commented 8 years ago

You can run Heroku stuff locally with:

https://devcenter.heroku.com/articles/getting-started-with-python#run-the-app-locally

Sounds easier than Apache.

seansaito commented 8 years ago

I think making connections to S3 occasionally caused errors. So hopefully the transition to local static files would prevent these from happening.

seansaito commented 8 years ago

Anymore now? Otherwise I will close the issue.

virgil commented 8 years ago

Close it. On Wed, 20 Jan 2016 at 00:39 Sean Saito notifications@github.com wrote:

Anymore now? Otherwise I will close the issue.

— Reply to this email directly or view it on GitHub https://github.com/seansaito/Roster/issues/7#issuecomment-172910492.