Custom Query (11 matches)
Results (7 - 9 of 11)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #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. |
|||
| #7 | worksforme | managing trac.ini | ||
| Description |
A minority of web admin tasks affect the trac.ini file. This means we cannot implement another management procedure for those files without taking account of the concurrent management of the file by two procedures. One possible such procedure was to have the hourly cron job update trac.ini from the project's svn repository. This would overwrite changes made by web admin, and it might change trac.ini to owner root, whereafter web admin (www-data) would be unable to change it. Perhaps that is the solution, make the file root-owned so that web admin's attempts to change it fall over, thus encouraging developers to make those changes by hand in the svn repository. But how badly does it fall over? |
|||
