Custom Query (11 matches)
Results (1 - 3 of 11)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1 | fixed | use of example.org | ||
| Description |
New projects are configured such that their wiki refers to example.org. The new trac.ini file has this as "url", as "link", and "descr" is set to "My example project". We should routinely change these to make sense for the server or the project. |
|||
| #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. |
|||
| #2 | fixed | projects need trac-admin | ||
| Description |
At least the main developer in each project needs to be able to configure at least the tracker. Not all software consists of "component1" and "component2". Haha. Some projects have three components, others might want to name their components in Gaelic. |
|||
