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 [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Hi,
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 http://preeminent.org/squeak/tut2007/html/128.html Feel free to ask more specific questions :-) Cheers Matthias On Tue, May 13, 2008 at 7:35 PM, Chris Dawson <[hidden email]> 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 > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Chris Dawson
Hi Chris,
We use Monticello as follows. For each project we have an empty root package with dependencies to all other packages (including for example Seaside). In general, you commit the root package to the repository to keep different versions of different packages together. In addition we use MC configuration maps for development, testing and production image configurations. The dev map, for instance, has additional packages like eCompletion and Shout whereas production configuration for example includes a vnc server. Then we have an automatic build system that grabs new maps and builds images from scratch. HTH, Adrian On May 13, 2008, at 19:35 , Chris Dawson 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 > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |