Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi all,
is it ok to checkout modules/submodules into a sandbox of any other module?
I've done some tests and it seems ot work but before I start using such
a setup in a production environment I'd better backup that by someone else'
knowledge.
Some more infos to better explain why I want to use it that way
I have a growing number of different software projects I'm working on
with a business partner as well as with some external companys/freelancers.
In general I like to have as much project related stuff within the project
folder as possible, this includes typically "public" stuff like art-assets,
source code, master/release builds, documentation but also internal infos
like contracts, sales results etc. only meant to be viewed/changed by my
bussines partner. It may be also some core technology I do not want to
share with contractors or whatever (so the public part would f.i. only
contain a library but not it's sources).
It would be possible to handle these conditions with ACLs but that would
be more work to maintain and have to be done again for each new project.
By using one internal repository with modules containing only internal
subdirs I only have to tell my partner once how to handle/checkout it
and we're done "forever".
Using modules/2 would be another possibility, but I aim at the most simple
and flexible solution with as little adminwork as possible (as I'm already
work-overloaded :-)) I guess behind the scenes what I like to do is
probably the same as using a modules file?
A virtual setup would look like that:
game1module\
\assets
\docs
\releases
\sources
internal\
game1module\
contracts\
sales\
sandbox
game1module\
\assets
\contracts (internal\game1module\contracts)
\releases
...
Thanks in advance for any responses and best regards,
Michael