spmurrayzzz

34 ms·

361.
by spmurrayzzz 14y ago
I just don't think I did a great job of reading the article. Re-reading it now, it seems that a similar assertion was made that was somehow lost on me. I think the point of 'use your webserver, not Django' was likely not highlighted enough
362.
by spmurrayzzz 14y ago
There's something I'm not clear about with respect to the stated problem. I have wrestled with the Django static dance myself, but the most obvious solution (to me at least) was to add a `location` section to my nginx config pointing to my
363.
by spmurrayzzz 14y ago
Maybe devtable[1] could be extended in a way thats a little more bent towards code education. [1] http://try.devtable.com/
364.
by spmurrayzzz 14y ago
I found myself similarly vexed when I first tried to deploy a Django project. Turns out I was making the process far more complicated by trying to wrestle with mod_wsgi and Apache. I found that nginx + FastCGI[1] was by far the easiest conf
365.
Your Next Smartphone Screen May Be Made of Sapphire(technologyreview.com)
7 points by spmurrayzzz 14y ago|0 comments
366.
by spmurrayzzz 14y ago
Maintainer seems to be aware of the need to keep a conventional RESTful approach. The default state for `routes.js` includes a commented section about setting up HTTP verb routing.
367.
by spmurrayzzz 14y ago
If I'm not mistaken, the prevailing precedent here is found in Lamparello v. Falwell ( 420 F.3d 309 4th Cir. 2005 ) "On appeal in 2005, the United States Court of Appeals for the Fourth Circuit reversed the earlier decisions, ruling that th