Changes between Version 5 and Version 6 of TracMultipleProjects/ComprehensiveSolution

Timestamp:

Jun 24, 2007, 6:50:08 PM (17 years ago)

Author:

Dave Abrahams <dave@…>

Comment:

—

TracMultipleProjects/ComprehensiveSolution

@@ -25 +25 @@
 == Just How Comprehensive Is This Solution, ''Really?'' ==
 
-Ticket [#130] contains a long, rambling, and extremely enlightening discussion of what people need from MultiProject support.  Anyone who has read that thread, and the [TracMultipleProjects other pages] proposing different ways to support multiple projects, knows that my solution isn't going to work for everyone.  Nonetheless, I think I've hit a "sweet spot" that gives most people most of what they're looking for, and more importantly, can be (relatively) easily set up today by anyone.  So while my claim of having a "comprehensive" solution might be seen as grandiose, I think it's supportable.
+Ticket [#130] contains a long, rambling, and extremely enlightening discussion of what people need from multi-project support.  Anyone who has read that thread, and the [TracMultipleProjects other pages] proposing different ways to support multiple projects, knows that my solution isn't going to work for everyone.  Nonetheless, I think I've hit a "sweet spot" that gives most people most of what they're looking for, and more importantly, can be (relatively) easily set up today by anyone.  So while my claim of having a "comprehensive" solution might be seen as grandiose, I think it's supportable.
 
 == Requirements ==
 
- * You'll need to patch your Trac with the solution to ticket:4547.  The latest at the time of this writing [#4547/datefmt-r5696.diff].
 
 == Motivation ==
@@ -38 +37 @@
 
 It doesn't work to ask our customers to [TracMultipleProjects/SingleEnvironment share the same Trac instance]. Customers need privacy, and Trac isn't yet up to the task of [TracDev/SecurityBranch managing fine-grained permissions] on individual [WikiContext resources].  Sometimes we're working on proprietary software that ''must'' be kept private, but even when we're working on open source, customers generally feel more comfortable when their issues are not exposed to the world. 
+
+== Troubleshooting ==
+
+I have applied a few small patches to my local trac installation to work around various bugs in Trac or in plugins.  I'm not sure that these bugs will show up for you when implementing this solution (and it's very likely they've already been fixed by the trac team), but in the interest of full disclosure, here they are:
+
+ * ticket:4547 describes a problem where python generates errors because {{{datetime}}} objects and numeric types such as {{{float}}} don't interoperate.  The latest patch at the time of this writing is attached to the ticket: [#4547/datefmt-r5696.diff].
+ * If Trac tells you to run "{{{trac-admin /path/to/your/environment upgrade}}}, and it fails with "{{{iteration over a non-sequence}}}", apply the tiny patch shown in #5593.