Absolutely, Sean, that's exactly what I'm asking for. Thank you so much<br>We make a very similar assumption<br><div id="result_box" dir="ltr">We must review our habits to avoid the use of ZOBD to develop (yes, we use plone3)<br>
</div>Again, thank you so much. You help us a lot!!!<br>Cheers!<br><br><div class="gmail_quote">2008/6/18 Sean Upton <<a href="mailto:sdupton@gmail.com">sdupton@gmail.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Jun 18, 2008 at 2:51 AM, Garito <<a href="mailto:garito@sistes.net">garito@sistes.net</a>> wrote:<br>
> What I would like to know is how I use git to work with my workgroup<br>
> Do I use only a centralized zope/plone or I need to install them for every<br>
> member of the workgroup?<br>
<br>
</div>I'm supposing you are doing python package and Zope2 Product<br>
development, and in this case you definitely want each developer to<br>
have their own checkout(s) of code as a working copy on their own<br>
workstation or personal space on a shared server. It is likely you<br>
want to use separate databases (Data.fs) files for development (and<br>
periodically keep them in sync by copying a packed copy of the<br>
database from a central place). If you wish to use a shared database<br>
late in development, you can use ZEO or Relstorage to host the<br>
database over the network and have each developer workstation connect<br>
to that. I would not recommend a shared database for early<br>
development on any project, just for late-stage development and<br>
testing.<br>
<div class="Ih2E3d"><br>
> Witch parts of zope/plone can I put on it?<br>
<br>
</div>If you are developing on top of Zope and Plone, you likely do not need<br>
either of these in svn/git, just your own Python code packages. With<br>
svn you can alternately create "bundle" checkouts of your own modules<br>
and products interspersed with checkouts from svn of third-party<br>
modules you are using. You would only version-control code, not<br>
content in the database.<br>
<div class="Ih2E3d"><br>
> I would like to use a control version manager but I have no idea how to<br>
> configure my space, witch files can I control and so on<br>
<br>
</div>see above.<br>
<div class="Ih2E3d"><br>
> In a ruby on rails scenario I create the RoR project and a database then I<br>
> create a git repository and begin to work (some commits here)<br>
> Then if some other members join to the project I make a checkout from the<br>
> master repository and begins to work all with the same database<br>
<br>
</div>You can do this, if you want; see above. Again, I recommend against a<br>
shared database early in development; there is more that can go weird<br>
in ZODB than in ActiveRecord fronted RDBMS on a shared copy in early<br>
development.<br>
<div class="Ih2E3d"><br>
> But I zope/plone I can't figure out what files I put to the repository and<br>
> what happens with data.fs (some modifications are made in the database, what<br>
> happend with them? I suppose I can't control them with subversion/git)<br>
<br>
</div>You do not want to fork zope or Plone, but develop your own packages<br>
on top of them. That should make this easy, only modify your own<br>
code, unless you absolutely know what you are doing. There are other<br>
ways to modify behavior of other Products and the platform (monkey<br>
patching, subclassing existing components, writing new skins, creating<br>
generic setup profiles).<br>
<br>
Stuff in the database is not in svn; do not put code in the ZODB (e.g.<br>
templates edited through-the-web, though this is possible in some<br>
cases with some Plone skin code). Keep code on the filesystem.<br>
Content is not versioned in svn, if you need revisions of content<br>
objects in the database stored in a CMS like Plone, there are other<br>
mechanisms for that (e.g. CMFEditions is part of Plone 3.x).<br>
<br>
I hope this helps.<br>
<font color="#888888"><br>
Sean<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mis Cosas<br><a href="http://blogs.sistes.net/Garito">http://blogs.sistes.net/Garito</a><br>Zope Smart Manager<br><a href="http://blogs.sistes.net/Garito/670">http://blogs.sistes.net/Garito/670</a>