Also, one of the things you mentioned (about security updates of the chroot) is something i have been pondering today. Although a single compile will mean recompile everytime a security announce is released, this is unavoidable.
This is my idea for handling security announcements: The single binary will have support for monitoring various sources for indications as to whether or not there is a security announcement for one or more of its internal componants. Within the configuration, the user can set an email address which these alerts are sent to. To avoid any single person being the weak link, we'll make it monitor not only the official project announce, but also remote security repos, to give it hints as to whether or not there is a security release for any specific component. The above idea will need some tweaking ofc, or maybe someone else could think of a better way to do this..? This also makes me think about build control. I guess each project would end up having a build file for future rebuilds, would it be wise to integrate this into the binary, as a backup incase the original is lost?? So many thoughts.. Cal On 8 Jul 2011 10:47, "Cal Leeming [Simplicity Media Ltd]" < cal.leem...@simplicitymedialtd.co.uk> wrote: > Hi Bjarni, > > Thanks for your input. As pointed out earlier in the thread, the end goal is > to provide a single binary that is entirely host independant, contains the > chroot/stack needed by the webapp etc. > > You really need to watch the facebook video link i included earlier in the > thread to understand what we're trying to achieve. > > Im drawing up the design principles today, which should give you a better > idea.. but in a nutshell, imagine a single binary which would run entirely > from memory, be completely host independant, contain everything the webapp > needed (stack/chroot/deps etc), and have a nice ncurses interface to > configure this all from (with features like automatic memory usage > calculation / configuration - something which is overlooked oh so many > times) > On 8 Jul 2011 08:53, "Bjarni Rúnar Einarsson" <b...@pagekite.net> wrote: -- 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.
