you won't want that, since both things will include 'gentlecat'
so the client one will kill the server and vice versa
I'd have do /home/gentlecat/...venv/bin/python (i.e., use the full path), and then replace 'grep gentlecat' with 'grep client.fcgi | grep gentlecat'
(or server.fcgi, for that one, obviously)
probably could be done with one grep but it doesn't really matter, so :)
oh, also full path
the DB is created, incidentally
seems to still be 500ing, not sure why
oh, I guess I haven't actually done the table-making and such, though you can probably do that
I've done what python manage.py create_db would do, anyway, if somewhat more manually
the pastebin looks right at this point as well
if you don't know screen: 'screen' creates a new one, then you can run one of them, then "ctrl-a c" will create a second window in which to run the other, ctrl-a n/p to move to next/previous window and ctrl-a d to detach; screen -ls will list current screens and screen -rd will reconnect if there's only one; if there's more than one you'll have to specify a process number or such, which you can get from screen -ls
that's some cool magic, looks like i've got both server and client running
still getting 500 though
yup, getting errors rather than 502s on both
I assume tables/fixtures still need inserting, anyway, but as mentioned I think you can do that without me, so
if that's still the onerror callback that won't help, because the issue is the onerror callback not firing
right, I need to call that for every image
yeah, but if you already have a src set, that's the issue
you need to set the error callback before setting the src at all; it looks like what you're doing there is setting the src to the same thing after setting the error callback
which won't work because the browser won't rerequest the image if it already knows it's missing, and thus won't fire the error callback
I updated last pastebin
yeah, that looks right
but that seems kind of hacky
it definitely is hacky, yeah :/ not much to do about it
I guess we'll have to wait for API fixes
there's other methods of trying to see if an image loaded correctly (img.complete and image.naturalWidth seem to pop up fairly often, but neither is supported everywhere), none that are events quite the way you'd probably want
img error events don't bubble, as I recall, which prevents the potentially-nice option of putting it on <body> or something
another option would be something server-side, I guess, that tries to load the image, and if it works return a redirect to it, otherwise a redirect to the not-found image?
arguably that'd be a good thing to add to caa.org, even, just an extra parameter for something to 307 to in case of a 404, rather than just 404ing
but wouldn't server side checking increase page load time?