Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
02/11/10 07:51:29 (14 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
- Property Owner changed from dzmacdonald to jmoore
-
Property
Priority
changed from
critical
to
blocker
-
Property
Summary
changed from
Permissions problem with Scritping service
to
Permissions : problems with Scripting service
-
|
initial
|
v2
|
|
| | 1 | |
| | 2 | Scripts are an interesting problem for #1434. They are one of the few (the only?) case of data in the "system" group that is intended for use by others. To make this work, we will most likely need special handling until the FS solution is ready. |
| | 3 | |
| | 4 | == Issues == |
| | 5 | |
| | 6 | * #1315 (ScriptI sets permissions) is no longer allowed. Will's issue below |
| | 7 | * Users would have to log into "system" to see the admin scripts |
| | 8 | * Linking between the admin scripts and the result files is not allowed. |
| | 9 | |
| | 10 | (Partial) Options: |
| | 11 | * Make "system" public |
| | 12 | * Allowing linking to "system" objects |
| | 13 | * Cons: how to handle chgrp? |
| | 14 | * Have the same scripts in each group |
| | 15 | |
| | 16 | ---- |
| | 17 | |
| | 18 | From Will: |
| 1 | 19 | Couldn't upload a script. |
| 2 | 20 | Using server r6063. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.13467 sec.)
