#493: Use trac with a remote Subversion repository
--------------------------------------------------+-------------------------
Reporter: [EMAIL PROTECTED] | Owner: cmlenz
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: version control | Version: 0.9b2
Severity: normal | Resolution:
Keywords: subversion svn remote repository svk |
--------------------------------------------------+-------------------------
Comment (by anonymous):
Any experienced IT administrator knows that keeping multiple services on
one box does not "save work". This is the single reason why we cannot
adopt Trac for any real project in our organization. We have an
established SVN repository, processes, and security policy and there is no
way we could install Trac on the SVN server. The SVN server is considered
security and mission critical.
If there would be a way to somehow relay authorization from the user's
desktop to the SVN server through Trac, that would be perfect. This way
we could set up Trac without having to let our IT department set it up
(which would take months to actually happen). We could update to a new
release and apply patches whenever we need to. Currently, we cannot,
since setting up Trac requires all-permissive access to the SVN repository
and that means it would have to be administered by the IT guys. If Trac
could offload all real authentication and access control to SVN, our IT
would be happy.
Anyway, just the possibility to access a remote SVN repository is needed
for our IT to even consider setting up a Trac server.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/493>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
