flashingpumpkin

I've got to disagree with the chapter about settings files. Instead of maintaining multiple different settings for different environments, make your default settings file pull modifications for each environment from os.environ, e.g.:

  STATIC_URL = os.environ.get('STATIC_URL', '/static/')

This is a lot saner and won't descend into a mess that is keeping multiple settings files around. It's also a lot easier to explain.

This. And if you don't want to go to the length of maintaining your own Chef server you can opt for hosted Chef:

http://www.opscode.com/hosted-chef/

Here's [1] an interview Nick gave just a couple of hours ago on Bloomsberg.

[1] http://www.bloomberg.com/video/slacker-16-year-old-whiz-laun...

I think it's also worth linking to David Beazley's Curious Course on Coroutines and Concurrency [1]. It's exploring the ideas of a task scheduler implemented in Python. This article reminded me of it. It's not a full VM, but about half way into the PDF he goes into quite some detail on how to build a task scheduler modelled after an OS and how it works in an actual OS. Give it a read.

[1] http://www.dabeaz.com/coroutines/

The issue I had with Pyjamas is that the whole tool-chain and compilation was a bit borked and the documentation a bit vague. After playing around with it for a day I decided it was too cumbersome so I ditched it in the end and tried py2js which Pyjaco is forked from. Mind you that was 2 years ago so a lot might have improved in that time but it convinced me that writing JS in Python is (was) not really feasible.

I really like that they opted to do everything over SSH in contrast to both Chef and Puppet that need a client/server configuration or at least some of their packages installed locally.

We do all of our deployments with Chef Solo and push our Cookbooks via Fabric over SSH to our servers. Pallet is definitely something to have a deeper look at as I don't like installing more than the bare essentials of what our apps need on our servers for various reasons.

Looks like the host is not quite keeping up anymore - cached version: http://webcache.googleusercontent.com/search?q=cache:aviflax...