Discuss Scratch
- chipmunkmc
-
Scratch Team
59 posts
Website development
Cloud variables are finally fixed on the scratch-www side of things… unfortunately this does not mean they work just yet. And yes, I implemented a hacky workaround for paths not being supported as cloud hosts, so it should work just fine on the .onion and future .i2p domains.
- max
-
Scratch Team
3 posts
Website development
Okay so just a moment ago, the site slowed down to the point of returning 504 Gateway Timed Out, however I seemed to be the only user actually making requests to it the whole time according to nginx logs, so it doesn't seem like a (D)DoS.
Somehow the logs lack any recent, useful info, at least AFAIK.
I'm pretty sure I've seen this happen previously too.
Somehow the logs lack any recent, useful info, at least AFAIK.
I'm pretty sure I've seen this happen previously too.
- max
-
Scratch Team
3 posts
Website development
I'd also like to note that I properly configured logging for APIClone so it should be easier to debug things.
Also I've had the timeout issue multiple times on daphne but only once (or twice?) on gunicorn, interestingly.
Also I've had the timeout issue multiple times on daphne but only once (or twice?) on gunicorn, interestingly.
- max
-
Scratch Team
3 posts
Website development
I also decided to finally set up apiclone on my main PC for development, it was quite simple and I should have done so sooner. This did lead to me catching a bug in apiclone causing the admin panel to be inaccessible though!
Anyway I keep getting this error:
It's been this way for a while and I've been able to safely ignore it, but it's still quite interesting. It never occurred on my local installation, notably.
Anyway I keep getting this error:
Your models in app(s): 'djangobb_forum', 'homepage' have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
It's been this way for a while and I've been able to safely ignore it, but it's still quite interesting. It never occurred on my local installation, notably.