[Camps-users] Can camps restrict access?

[Brian J. Miller]

Grant wrote:
> I'd like to hire a freelancer to work on my Interchange website.  I
> don't want to provide access to all of my code, but instead only the
> particular file or files being worked on.  Can camps help restrict
> access to all but the specified file or files?  If not, does anyone
> have an idea for facilitating that sort of access restriction?
> 
> - Grant

Not really that I know of. The camp needs a full check out of the source 
tree, whatever portion of that source tree is required at least. So 
restricting access, particularly read access, to a subset would likely 
prove difficult. I've gathered you can do this sort of thing with 
Subversion repos but can't say I've tried or heard of such a thing with 
camps.

Two alternatives come to mind depending on what kind of files you are 
meaning. You could move them out of the primary repo itself by using:

1) The copy paths configuration such that they aren't a part of the 
repository at all, that way a camp could be set up to have its symlinks 
point to files on some secured part of the FS, then updating the files 
in that location would appear to have them updated in the served 
version. Assuming a server restart is not required to make them take 
affect this should work, and there is no reason that alternate location 
couldn't be under version control (albeit not part of a camp's).

2) Isolate the files into a submodule and then only allow cloning of 
that submodule. This would take more work and would require some sort of 
merge setup using publish hooks or similar.

HTH,

-- 
Brian J. Miller
End Point Corp.
brian at endpoint.com