Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

> >> > > I assume _start / _end / _size are references to the address space (within > the binary) where these embedded binaries (in symbol form) are kept?? yes, exactly > > Is there any sort of restrictions on maximum allowed symbol size? (looked > on > Google, but couldn't find anything)

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

*Roberto: *my responses below! *Everyone else: *Roberto has very kindly done some modifications to uwsgi to get things moving. See below comments for more info :) On Sun, Jul 10, 2011 at 6:57 PM, Roberto De Ioris wrote: > > >> > > > > I'll pull the most recent code tomorrow,

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Fri, Jul 8, 2011 at 5:37 PM, Brian Bouterse wrote: > I'm going to try to get a pypy installation built from source that has > nginx/gunicorn/django. I will share back what I can come up with. If anyone > else is doing similar things share back your findings please. I'm

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

I'm going to try to get a pypy installation built from source that has nginx/gunicorn/django. I will share back what I can come up with. If anyone else is doing similar things share back your findings please. I don't use shed skin, but I believe pypy is much more mature. As evident from the

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Fri, Jul 8, 2011 at 3:53 PM, Venkatraman S wrote: > Cal, > > Quiet frankly, it looks to me that if you are spending some effort on this > - better start with django on pypy. > And then probably we can move to 'one-binary' idea. I much prefer the idea of a true single

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Cal, Quiet frankly, it looks to me that if you are spending some effort on this - better start with django on pypy. And then probably we can move to 'one-binary' idea. -V -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

I'd imagine this would probably join the same bucket as "shedskin", as it's experimental, lacking feature support, and little known compatibility testing. On Fri, Jul 8, 2011 at 3:35 PM, Venkatraman S wrote: > And btw, AlexGaylnor, recently wrote a python >

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Fri, Jul 8, 2011 at 3:24 PM, Brian Bouterse wrote: > I've been thinking about this for a day or two now, and here are some > thoughts: > > One option to possibly compile python to C++ is shed > skin, > to translate python code into a C

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

And btw, AlexGaylnor, recently wrote a python decompiler; probably this can be leveraged ? -V -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Fri, Jul 8, 2011 at 7:54 PM, Brian Bouterse wrote: > I have also heard of folks using pypy in production serving django sites, > so I think Django is ready for this. Interesting. Can you share more on this. Any caveats/tradeoffs? -V -- You received this message

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

I've been thinking about this for a day or two now, and here are some thoughts: One option to possibly compile python to C++ is shed skin, to translate python code into a C binary. Note that the compiled C code is statically compiled which produces a C

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Here is what I've come up with so far: https://github.com/foxx/jennifer/wiki/Design-Sketch I've enabled public edit mode, so feel free to add/change. Cal On Fri, Jul 8, 2011 at 10:55 AM, Cal Leeming [Simplicity Media Ltd] wrote: > Also, one of the things

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

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

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

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

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Fri, Jul 8, 2011 at 5:22 AM, Roberto De Ioris wrote: > > 2011/7/8 Bjarni Rúnar Einarsson > > > > Nice script; but i (and also i guess Cal) were thinking more in the terms > > of having a single binary. > > > > [DISCLAIMER] i still have not tried pybreeder

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

> 2011/7/8 Bjarni Rúnar Einarsson > >> >>http://pagekite.net/wiki/Floss/PyBreeder/ >>https://github.com/pagekite/PyBreeder >> >> It's basically a small tool for combining multiple .py files into one. >> It's trivial I know, but I looked all over and couldn't find

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

2011/7/8 Bjarni Rúnar Einarsson > >http://pagekite.net/wiki/Floss/PyBreeder/ >https://github.com/pagekite/PyBreeder > > It's basically a small tool for combining multiple .py files into one. > It's trivial I know, but I looked all over and couldn't find anything quite

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

I actually just wrote a similar tool for solving a (very limited) subset of this problem: http://pagekite.net/wiki/Floss/PyBreeder/ https://github.com/pagekite/PyBreeder It's basically a small tool for combining multiple .py files into one. It's trivial I know, but I looked all over and

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

THIS. IS. SPARTA!!! On 7/7/11, Cal Leeming [Simplicity Media Ltd] wrote: > Hydra is already a used package name in Pypi, and a few other code > related projects (would prefer to use a name which isn't already used > in a similar area). :/ > > On Thu, Jul 7,

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Hydra is already a used package name in Pypi, and a few other code related projects (would prefer to use a name which isn't already used in a similar area). :/ On Thu, Jul 7, 2011 at 5:28 AM, Venkatraman S wrote: > > On Thu, Jul 7, 2011 at 9:40 AM, Roberto De Ioris

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Also, thanks Roberto for suggesting Silver Lining, it's certainly given me some food for thought :) On Thu, Jul 7, 2011 at 1:28 PM, Cal Leeming [Simplicity Media Ltd] wrote: > Hi Roberto, > > As Venkatraman said, Silver Lining seems to be aimed more at

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Hi Roberto, As Venkatraman said, Silver Lining seems to be aimed more at distribution. Also, they have stated in the docs that it is locked down heavily to the host OS, and it would appear that the whole thing is tied into libcloud (which is completely the opposite from the direction we want to

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Thu, Jul 7, 2011 at 9:40 AM, Roberto De Ioris wrote: > http://cloudsilverlining.org/ > This looks more like a deployment configuration script than compiling into a binary. I would be very much interested in the latter. Thanks for sharing though. -V -- You received this

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Il giorno 06/lug/2011, alle ore 21.03, Cal Leeming [Simplicity Media Ltd] ha scritto: > 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

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Thu, Jul 7, 2011 at 1:43 AM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote: > I've created a place holder on Github for this. > > Unsure what to call it yet, so it's temporary name is Jennifer. > > https://github.com/foxx/jennifer > > Future name suggestions

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

I've created a place holder on Github for this. Unsure what to call it yet, so it's temporary name is Jennifer. https://github.com/foxx/jennifer Future name suggestions are very much welcome lol. Cal On Wed, Jul 6, 2011 at 8:46 PM, Brian Bouterse wrote: > I write a lot of

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

I write a lot of automation on RHEL / CentOS systems and would like to see the built process to look at potentially porting it. Let me know how I can follow the development. Brian On Wed, Jul 6, 2011 at 3:29 PM, Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> wrote:

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Wed, Jul 6, 2011 at 8:15 PM, Shawn Milochik wrote: > It definitely sounds interesting. I'd like to hear more about it as it > develops. The only quibble I'd add is to not limit it to Ubuntu. I use > and love Ubuntu, but I suspect that a lot of people who would want the >

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

(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

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

On Wed, Jul 6, 2011 at 8:14 PM, Thomas Weholt wrote: > Anything that can make django/python-based webapps easier to deploy is > interesting. That's been the huge thing for all my PHP-friends; the > ease of deployment. Now if we had something similar for django/python >

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

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

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

It definitely sounds interesting. I'd like to hear more about it as it develops. The only quibble I'd add is to not limit it to Ubuntu. I use and love Ubuntu, but I suspect that a lot of people who would want the ability to obfuscate code and deploy easily to client servers would be using RHEL or

Re: Some thoughts on a package/stack compile system for easy distribution of webapps..

Anything that can make django/python-based webapps easier to deploy is interesting. That's been the huge thing for all my PHP-friends; the ease of deployment. Now if we had something similar for django/python ... it would rock! :-) Used java for some years and war-files worked ok as well. And

Some thoughts on a package/stack compile system for easy distribution of webapps..

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