Custom Query (11 matches)
Results (4 - 6 of 11)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4 | fixed | projects need to grant svn access | ||
| Description |
The developers on a project can use the web admin plugin to change which existing users can access the trac environment (including browsing the repository), but proper access to the svn repository via HTTPS/WebDAV is firmly under control of the superuser on the server. Could the per-project group definitions in dav_svn.authz be collected automatically from projects rather than the whole file be edited centrally only by root@forge? |
|||
| #5 | fixed | remote user creation | ||
| Description |
The user access management per project by its developer (ticket #4) points the way to remote user account management also. We can have another Perl CGI script running as root, which checks out the passwd file from the ROEadmin repository. Any developer on the ROEadmin project can then remotely check out, modify and commit the passwd file, then invoke the CGI script to put the file where it has an effect. |
|||
| #6 | fixed | no e-mails | ||
| Description |
There are no e-mail notifications, even when an e-mail address is entered into the Cc field of a ticket. |
|||
