[Seaside] Deploy via...image or monticello?

Steven Baker steven at stevenrbaker.com
Thu Jul 1 02:50:16 UTC 2010

See the Version Uploader.


Of course, you can automate this with curl and/or some ruby scripts.

On Wed, Jun 30, 2010 at 7:47 PM, Pat Maddox <patmaddox at me.com> wrote:
> I'm having a lot of fun learning Seaside (again - have had several false starts, but I'm sticking with it this time! :)  But I'm still a bit lost when it comes to deployment.  I've figured out that the first step is uploading an image to the server, and running from that.  I have trouble after that though.  How do you keep the image up to date?
> One option is to upload a new image after I've made changes locally - but that will blow away any data on the server.  So it makes more sense (in my code-as-files-centric view of the world) to commit changes to monticello, and then update the server's image from that.
> That leaves me with the question of how to keep *other* stuff up to date, other than what I have personally coded.  If I've updated / installed packages locally, I'll need to keep track of that somehow so that I can make the same changes on deploy.  Right?
> I just finished reading through the Deployment chapter of the Seaside Book (skipping ahead several chapters...).  It looks like the answer is monticello.  I'm curious to know how folks handle the issue of knowing everything they need to update / install to make it work.
> Pat
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list