I'm new and need some general advice/help

adamjon858 adamjbratt at gmail.com
Fri Jan 7 10:47:23 CST 2011


Hey, I just started using Mercurial for a module based CMS written in PHP.

However, I'm not sure the best way of setting some stuff up. For certain
types of websites/clients we need specialized versions of the CMS but we
don't want to have these completely unlinked from the originals.

Is there a way to setup repositories like this?

-Main repository where main system is located and updated
-Linked to the main repository are repositories or something for each
module. By default, only the cms, auth, and image modules are pulled when
you pull the main repository. So basically any other module has to be pulled
separately.
-We'd also like to have a separate repository for each website we do. Then
when we do custom work for each website we would push to that repository.
However, and here's the big question, we'd also like to be able to update
these separate repositories when we push changes to the main repository. For
example, if we changed the index.php in the main repo we would want it to
also push those changes to the sub-repos for each site. If the code in the
subrepo has been changed for that file since the last push to the main repo
than it will prompt to merge for each subrepo
-We'd like some way to push changes to all of the subrepos from the main
repo whenever we'd like so when we release a new version of the base cms we
don't have to individually push changes to each subrepo

We're currently using bitbucket but I don't know if this will all be
possible on their servers.

Any help would be GREATLY appreciated.
-- 
View this message in context: http://mercurial.808500.n3.nabble.com/I-m-new-and-need-some-general-advice-help-tp2212869p2212869.html
Sent from the General mailing list archive at Nabble.com.


More information about the Mercurial mailing list