(sorry for the double post - should have included this in the original thread)

http://www.facebook.com/video/video.php?v=10100259101684977

It's *well* worth watching though.. Put an hour aside, make a cup of tea etc :)

Cal

On Wed, Jul 6, 2011 at 8:18 PM, Brian Bouterse <bmbou...@gmail.com> wrote:
> What is "the Facebook video" you speak of?  I didn't see it.
>
> On Wed, Jul 6, 2011 at 3:03 PM, Cal Leeming [Simplicity Media Ltd]
> <cal.leem...@simplicitymedialtd.co.uk> wrote:
>>
>> Hi all,
>>
>> After seeing the Facebook video about how their development team
>> compiles everything into a single binary for easy distribution between
>> thousands of servers, I totally fell in love with the idea. Although
>> their approach is to compile PHP into C, the same principle applies.
>>
>> The end result will be a single binary which will contain your webapp
>> + static resources + web server + application server, easily
>> deployable to many servers, and reduced time spent in managing the
>> stack (YMMV). Although I'm only going to be focusing on our needs to
>> begin with, there's no reason this concept couldn't be extended in the
>> future to include PHP, 32bit, other OS's etc.
>>
>> Some features I'm thinking of:
>>
>> * CLI based menu to build compile package (ncurses based). Easy to
>> use. Incorporates all features available in nginx/uwsgi. Comes with
>> 'basic' config mode (the bare minimal questions asked - for beginners
>> - which makes it almost impossible to build a broken package) and
>> 'advanced' mode which lets you change everything (with more risk ofc).
>> * Support for nginx + uwsgi + python2.6 + python2.7 + debian 64bit.
>> * Expose some sort of API which lets you query all aspects of services
>> running within the package (like nginx stats).
>> * Enable ability for nginx/uwsgi/python to log out to a syslog server
>> of some kind)
>> * Ability to obfuscate py code using various techniques.
>> * Maybe a test-run feature to test your package.
>> * Maybe some sort of MemoryError detection and reporting of such events.
>>
>> I'm probably going to make something like this for companies own
>> internal use, but wanted to see if anyone else had an interest in
>> seeing this go open source.
>>
>> Cal
>>
>> --
>> 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.
>>
>
>
>
> --
> Brian Bouterse
> ITng Services
>
> --
> 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.
>

-- 
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.

Reply via email to