convore.json/groups/django-community/amazon-machine-images-for-django/messages.json

[{"user_id": 24476, "stars": [], "topic_id": 19536, "date_created": 1302831966.427083, "message": "I found this, http://bitnami.org/stack/djangostack. But it's for django 1.3. anyone seen something similar, but for Django 1.2.5 ? This will simplify deployments.", "group_id": 81, "id": 693526}, {"user_id": 26944, "stars": [], "topic_id": 19536, "date_created": 1303033322.705003, "message": "Not really an answer but I'd be tempted to roll your own. Not too big a deal to install Django on a pre-existing AMI . I'm a bit anti on bitnami since I spent far-too-long trying to make one of their Ruby offerings work . Eventually I did it myself on a bog standard linux AMI. Probably at least half my fault but nevertheless did leave me feeling that I would do it myself in future.", "group_id": 81, "id": 716179}, {"user_id": 1736, "stars": [], "topic_id": 19536, "date_created": 1303062499.4140019, "message": "Using AMIs for deployment is rarely worth the trouble. Just start with stock Ubuntu LTS images and use something like Chef or Puppet to provision from there.", "group_id": 81, "id": 717777}, {"user_id": 13325, "stars": [], "topic_id": 19536, "date_created": 1303139949.07781, "message": "Since, in my opinion, one should have Django inside a virtual machine, you shouldn't need it in an AMI. Any lamp AMI should get you 90% there.", "group_id": 81, "id": 727257}]