On 26/01/13 02:02, Andy Burnett wrote:
Our requirements are pretty simple. We need a way of uploading an image,
and some standard for of persistence. At this point, we would be
perfectly happy to make compromises by agreeing that it had to be e.g.
Mongo or whatever (although ideally it would be gemstone). We just want
to make some progress on this.
I would prefer to upload a MetacelloConfiguration (or something similar)
instead of an image.
I like to think about the image as a temporary runtime. Not something
where I store code or someting I deploy. I would love to have something
like:
$ pharo -v 1.4-summer myProject.ston
where myProject.ston would contain all the necessary information to load
my project (dependencies, repositories, etc). This command would create
an image with my project on the fly from a stock Pharo 1.4-summer and
launch it. It would recreate the image everytime I want to work on my
project (or when it is deployed).
The problem right now is the loading time for dependencies (try to load
seaside in a pristine image, you'll get the point). All the other bricks
are there.
