[Seaside] version control usage for Seaside/Squeak

Matthias Berth matthias.berth at googlemail.com
Tue May 13 18:07:38 UTC 2008


I put all my code in a Monticello package. I save (publish) his
regularly to a local repository on my hard disk. I deploy initially by
copying the image to the production server. Then I can update that by
loading the updated monticello packages. Getting started with
Monticello was not that difficult, I guess "Squeak by Example" has
good up to date information on it. See also

Feel free to ask more specific questions :-)



On Tue, May 13, 2008 at 7:35 PM, Chris Dawson <xrdawson at gmail.com> wrote:
> Hi all,
> I'm new to Seaside and Squeak.  Monticello is a different version control
> system for me and I want to know how others are building and deploying their
> apps.  What technique do people use to build, test and then deploy.  I
> imagine I'll be developing locally on my laptop and then pushing to a
> hosting server.  I assume I don't want to use fileOut and fileIn to manage
> the code I write.  If you are open to sharing your code management
> solutions, I'd like to know.  I ask because there might be managment
> solutions that are not obvious to me as I am unfamiliar with programming in
> an image-based tool like Smalltalk/Squeak.
> Thanks,
> Chris
> _______________________________________________
>  seaside mailing list
>  seaside at lists.squeakfoundation.org
>  http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list