Web configuration/administration in addtion to trac-admin

[jonas]

The module should allow (trusted) users to configure
things like:

• User permissions
• Available ticket components, milestones, versions...
• Settings like theme, htdocs-location, cgi-name...

[jonas]

I just want to point out that you can use the text based
svn:trunk/scripts/trac_admin.py script until is web interface is added.

[daniel]

trac_admin.py is now called svn:trunk/scripts/trac-admin.

[daniel]

At some point we should obsolete trac-admin with a 'pure' web-based interface. Tentatively for 0.9.

[rocky]

I would recommend against obsoleting trac-admin. trac-admin is extremely useful for automating configurations. Plus, its a great way to initialize an 'admin' user with all access before even having to launch a web process. My recommendation would be to simply have both trac-admin and the web interface reuse the same core python code for doing stuff.

[daniel]

I agree with that.

[StefanW@…]

trac-admin is also useful for other (web)Gui-Programs to add new projects or edit project-permissions like it is on our small PHP-Web-Interface for adding new users, projects etc.
Pleople, who use (old? versions of) trac can use this for multiple projects.
If interested, download it from my server:
​http://www.whylee.at/opensource/projectportal.zip
(Sometimes my server does not have a good connection. try again i a minute)

I released it under GPL. If you can use it, fine. If you modify it and you think everone could use your modification, please send your modifications to me. ( whylee@… )

Geetings,

Weilhartner Stefan, 4ahead

[remi2402@…]

What about having a mix of both?

• Keep trac-admin for all administrative tasks as it stands today
• web interfaces for everything except low-level stuff (svn repos, trac env path, ...)

This way, TRAC_ADMIN users could manage almost all of trac without actually needing shell access. I, for one, wouldn't mind having this kind of possibilities.

Rémi
(faithfull trac user)

[daniel]

This is an important feature for 2.0

[Brad Anderson <brad@…>]

I've put together a bit of code for this.

See: ​http://68.91.106.142/projects/test/

and let me know if I'm on the right track.

[cmlenz]

I don't think we should push this to milestone:2.0, it's just too important a feature and should really make it into milestone:1.0. And now we have Brad working on a patch, too. :-)

My vote would be to put this on the plate for milestone:0.9.

[agizis]

Brad's demo seems like a huge step forward!

It's fine if things like themes stay done through files and command lines, but adding a milestone or component should be done through the web just like creating a ticket, because the project manager is probably just another web user, and not the system administrator.

Please, please, please, try to get this into 0.9!

[aadis-trac@…]

I also vote for 0.9, or at least 1.0.

Very useful feature

[jbolla]

At the very least, would like web interfaces to manage component, version, priority, and severity.

[brad <brad@…>]

The link I gave on Nov 8 has an IP address. It's still valid, but the vhost is not anymore. Use this:

​http://trac.dsource.org/projects/test/admin/ticket

[sreimers]

Any chance we will get WebAdmin capability in 0.9 timeframe? I just got the patch from brad working against latest trunk (rearch changes and all) - anyone interested in a patch?

[anonymous]

Yes it would be nice to post a patch here.

[Christian Parpart <trapni@…>]

I highly vote to be included with trac 0.9 :)

[sreimers <sven.reimers@…>]

Ok. Try to get it working with new pluggable architecture, and post it here afterwards. No patching necessary anymore, just some additional files if I understand new arch.

[cmlenz]

Okay, this isn't going to happen for 0.9, but it's highest priority for 1.0. Sorry.

[jeoffwilks@…]

I modified Brad's patch to work with the Debian Sarge 'trac' package (0.8.1-2, ~ r1310). I attached the patch to his Trac wiki at:
​http://trac.dsource.org/projects/test/wiki/TracWebAdminDevelopment

[mgood]

#1012 has been marked as a duplicate of this ticket.

[anonymous]

Eagerly awaiting this as well. :-)

[patrys@…]

Please leave me in the CC field, I am currently maintaining the PLD Linux spec file for Trac.

[anonymous]

Brad (& Jeoff) have done some good work here. I strongly feel that it would be better to have a partial webadmin implementation in 0.9 final than no web administration at all..

Agreed that trac-admin needs to always exist (makes automated installs a breeze), but that being the only practical way to administer basic things like components / versions etc does not impress PHBs who need to sign off on production Trac deployment.

[mgood]

Web administration is currently available for 0.9 as an external plugin: source:/branches/jonas-dev/webadmin

This will be packaged separately for now, and most likely bundled with 1.0.

[StefanW@…]

Editing Permissions for different projects and different users looks like this. svn-permissions is not finished yet and doesnt look that good

[anonymous]

User-interface-example how permissions could be handled:
As you can see in the attached image tracperms.jpg, the user-interface is not 'compatible' to the trac-user-interface. We buildt our own development-portal in php where we can add new projects and users and adjust permissions for trac and svn. I think that if the developers from trac decide to add that permission-feature it would be cool if you make this suitable for a multi-project-configuration. Also svn-permissions would be fine. Thanks, WhyLee?.

(Our source is in php which uses the trac-admin command-line tool for modifying the permissions, 'direct'-intergration in python in trac would be a more elegant solution)

[whylee@…]

Example of a permission GUI for SVN (developed in php)

[cmlenz]

I'm working on integrating WebAdmin into the core for the next release.

[cmlenz]

Done in [4095].