20 Apr
2009
20 Apr
'09
6:42 p.m.
For WikiServer I SVN all the source code, the image/change, and the /
files.
At release time I ensure MC is updated for my project, quit the VM,
then commit everything to SVN.
This ensure I can later export a source tree from SVN for a particular
version and have everything the same as it was when I made the version
commit point.
Although this tosses 40-50MB of image/changes into SVN, disk space is
cheap.
That said a chore I have this week is to explore import/export to have
it build a zip file of not only the PRKernel, but /files as well.
But I'm not going to expect that should take over from my SVN solution
On 20-Apr-09, at 7:32 AM, Mariano Martinez Peck wrote:
Hi folks!
I was trying to see how to manage all my code and resources of a
Pier application. There are several things I must manage:
1) My library (css, js, and so on), seaside components, ...
2) External files ( /files )
3) Pier content (trough import/export utility)
For 1) I use Monticello.
But I don't know how to manage 2) and 3). I tough I could have a SVN
project where I can put them. So, what I should do is: export and
then commit SVN.
However, I would like to have all in the same control version
system. Is there a way I can do 2) and 3) in MC ?
Thanks in advance,
Mariano
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
=
=
=
========================================================================
John M. McIntosh <johnmci(a)smalltalkconsulting.com>
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
=
=
=
========================================================================