Reputation
1,443
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
3 15 39
Impact
~97k people reached

Feb
28
comment Disable caching when serving static files with Nginx (for development)
This seems to be the answer for me. The problem seems to occur with the specific combination of Sendfile, VirtualBox and an OSX host. abitwiser.wordpress.com/2011/02/24/virtualbox-hates-sendfile forums.virtualbox.org/viewtopic.php?f=1&t=24905
Jan
27
comment Upload everything with Knife
(I've accepted an answer now. I don't use Chef anymore, so I'm just trusting that CrackerJackMack's answer is valid.)
Nov
19
comment Fingerprint of PEM ssh key
That's incorrect. As @ominug pointed out above, ssh-keygen -yf does this.
Sep
15
comment Simple web tool for viewing log
It does look promising. Why not make that an answer instead of a comment?
Sep
8
comment How do I add Access-Control-Allow-Origin in NGINX?
That module seems to be compiled by default (at least on Ubuntu).
Mar
23
comment Disable caching when serving static files with Nginx (for development)
Ugh, ran into this as well. For clarity, the "server configuration" described above is the nginx config file.
Feb
11
comment Block employee access to public cloud
IMHO, blocking the 10 most obvious sites would probably achieve 95% of what management is after. No one cares about the few nerds that will tunnel around the block.
Feb
5
comment Protect a public-facing PostgreSQL server against abuse
Thanks for following up - I haven't got any further at the moment. I obviously have some reading up to do and need to redesign the servers to be both more robust and more replaceable.
Jan
29
comment How to prevent “ps” reporting its own process?
Yep, that works for me on OS X.
Nov
19
comment Protect a public-facing PostgreSQL server against abuse
The problem with restricting to actual .edu.au subnets, is it prevents people connecting from home, cafe wifi or from tethered mobile phones. Academics aren't as desk-bound as they used to be...
Nov
19
comment Protect a public-facing PostgreSQL server against abuse
So that the public can use it. Although, the audience is almost exclusively academics in Australia, so perhaps I should use network subnet restrictions?
Oct
9
comment Can't communicate with nginx from Vagrant host machine
Anything in nginx logs? Would tunnelling as a workaround solve your problem? What about doing the port forwarding using nginx?
Sep
10
comment nginx serving alternate location on 404
Thanks - useful comments. The extra "/tile/" rule is for other map styles which are rendered on this server (I left this unnecessary detail out). In this instance though, I don't really want a "root" - for most requests, there isn't a directory that I want to map onto exactly - they need to go through a separate server (either the local one on port 5005, or the remote one on port 20008).
Sep
10
comment nginx serving alternate location on 404
Sigh, I think I've found it. The local server is actually returning code 200 even when it can't find an image.
Sep
4
comment Continue running a task with terminal disconnected?
This explains it more: serverwatch.com/tutorials/article.php/3935306/…
Aug
26
comment Why is Postgres sitting 95% idle, with no file I/O?
Oh - that link had the answer. Yes, although there was "an index", it was just on the ID field, not the actual geometry field ("way") - so useless for spatial indexing. Frederik's comments contained the answer.
Aug
26
comment Why is Postgres sitting 95% idle, with no file I/O?
Thanks for pointing this out - I missed that. There are in fact two indexes on this table. Updating my question with more info.
Jul
19
comment “A” record redirect gives 400 Bad Request in nginx
This question appears to be off-topic because it is about
Jul
16
comment “A” record redirect gives 400 Bad Request in nginx
Hmm, nope. It's weird. www.mydomain.com works (even if I leave servername as localhost). The IP address works. But mydomain.com doesn't. (Both www.mydomain.com and mydomani.com resolve correctly).
Jul
16
comment “A” record redirect gives 400 Bad Request in nginx
Ok, strangely the problem seems to have fixed itself. Maybe something to do with DNS records?