Dev: - Ubuntu 11.04 (netbook) - vim - git - in-memory mocks of user DB - bundled Django dev server + PageKite for testing & showing coworkers
Production: - debian stable (linode) - redis for replicated user DB / sqlite for rarely-changing site content - lighttpd + fastcgi/flup (hot pages cached to static files for lighttpd to serve directly) - daemon wraps & restarts things that crash - yamon for black & white-box monitoring I also have a staging setup which is just like the production one, except it runs in a few local virtual machines which I expose them to the world (again for collaboration with remote coworkers) using PageKite. I'm pretty sure this is a relatively unusual setup, as I'm heavily biased towards using my own tools (eat your own dogfood, etc.). But it works for me! :-) (Aside: The site is so low-volume still that I do not know whether (or when) using SQLite this way will become a bottleneck. If anyone cares to enlighten me, that would be most welcome. I like it because copying the entire website around is super easy, making disaster recovery and off-line testing/curating quite easy.) -- Bjarni R. Einarsson Founder, lead developer of PageKite. Make localhost servers visible to the world: http://pagekite.net/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
