From: "Sam Ruby" <[EMAIL PROTECTED]>
> There are some things that I am very cautious about. Running scripts
under
> my id
It would not be a bad thing to make a "gump" id.
Permissions on the machine can be set more effectively to be tailored to the
Gump work, instead of your personal permissions.
> that copy files from one location to another on various machines
You should of course limit the places onto which the "gump" user can write
to.
> that
> have some relationship with Apache based on input from random repositories
> is one of them.
Random is not the case. You have to let them in.
What is really nissing is the possibility of having projects writing in
other project's workspaces.
This seems to be doable only programmatically, but it's not a big deal as
Stefan pointed out, since you control the workspace definitions.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
