Apr 24, 2011
I'm currently using SSH+SVN for a web project developed primarily in PHP. There is another developer working with me and we both check out from the repo into our own sandboxes which is viewable from the web. I want to bring in new implementers and restrict them to certain parts of the project code. How do I achieve this and still allow them to have a sandbox to preview the site with their changes in it?
View 2 Replies
For example, I have a piece of code called proprietary_algo.php that needs to be restricted to only privileged developers (read, write, execute). All other new implementers can still view the site via their sandbox, which requires the execution of proprietary_algo.php, but they cannot copy the code or read the code inside of it. I'm open to moving away from SVN or setting up a whole new process if I can achieve this. Added note: no, NDAs and trust will not cut it. For our business need and situation, the specific source files need to be restricted.
MORE INFO: I setup a virtual host and DNS that points to their sandbox dir [URL] so they can do testing. They checkout code directly from trunk into their sandbox and edit code on their IDEs remotely connected via SSH. As mentioned above, there are some code in the repo that should be off limits, but still needed to run the site when they edit and test in their sandboxes. All devs share the same MySQL DB instance.