Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I'm developing an application based on this structure :

/Root
/--- Index.php
/--- /includes/
/--- /modules/
/-------- /Mod1/
/-------- /Mod2/
/-------- /ModN/

In the future, 2 developers will participate in the project.

  1. I have to restrict the access for the developers. They shouldn't get access for the "/includes/" folder. It contains the system's Core. They just will have to code modules.

  2. I Will use Mercurial. What is the best "organisation" (repository, lock, permissions...) for this kind of project.

A need advices. Thank you :)

share|improve this question

closed as not constructive by Walter, Martijn Pieters, Robert Harvey, Glenn Nelson, Jim G. Jan 17 '13 at 23:14

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

add comment

1 Answer 1

up vote 1 down vote accepted

Perhaps you could create two repositories:

  • A "root" repository to hold Index.php and /includes
  • A "modules" repository to hold all the /ModN folders

then pull a local copy of the modules repository into /modules?

share|improve this answer
    
Thanks for your answer. If I do that, how can the other developer "test" their modules as it needs the system's Core ? give them a restricted access to a subfolder ? Is there a solution de deploy directly to FTP ? (I use Bitbucket) –  Cartha Jan 17 '13 at 21:47
    
@Cartha I'm guessing you'll have a server set up to do testing on, so if you give them access to the /modules directory there and let them update the repo (or have some sort of automated testing framework that could update it) then they could test it there. –  paul Jan 17 '13 at 21:57
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.