Hi Jeff, Is it possible to create an egg meta-package that includes Trac plus some useful subset of plugins plus some configuration for them?
>From my observations, newbies have problems when they 1) find good plugins; 2) find proper versions of the plugins; 3) find how to configure the plugins properly. As result, they say that Trac is hard to install/extend/maintain. Thus, it would be a good idea if there are packages like Meta-Trac-0.11-OpenPlans-1.0.egg, which includes Trac, plugins, and configuration tweaks. It looks that this will not only allow others to install Trac with plugins easily, but also it simplifies maintenance of existing Trac installations - the whole package can be tested/updated by a single command. This is just an idea, but it looks that it minimizes the Trac plugins hassle by reusing ready-to-go packages/configurations. Regards, Pavel On Fri, Jun 20, 2008 at 22:03, Jeff Hammel <[EMAIL PROTECTED]> wrote: > > There has been much discussion on this list and elsewhere concerning > installing trac + plugins out of the box, and probably doing configuration. > Several projects, such as oforge, already do this sort of thing, but there is > a perceived need for either other methodologies or perhaps more of a > community effort towards this solution. I'll going to share my methodology > that I use for installs and suggest a short-term methodology for trac-hacks > dealing with this issue. Nothing here is meant to obviate the need for > longer-term methodologies, such as (just naming random ideas I heard) making > plugins installable/browsable via the webadmin interface, setting up a PyPi > for trac-hacks, better orphaning and adoption of plugins, and other ideas > that can't (or at least won't) be done in a day. > > Installing trac is pretty easy. I'm going to (*) steps I find useful but > aren't strictly necessary. > > [0. install system dependencies (databases, svn bindings, python etc.) I'm > not going to touch these here] > > * 1. create a virtualenv ( http://pypi.python.org/pypi/virtualenv ) > > 2. install trac into the virtualenv > > * 3. install poacheggs ( https://svn.openplans.org/svn/PoachEggs/ ) > > 4. install plugins. For this i use poacheggs and a requirements file (this > one, though this version is somewhat outdated: > https://svn.openplans.org/svn/TracPlugins/plugins.txt ) > > 5. do the configuration. > > So the install process, minus the configuration, can be a 5ish-line shell > script. Its not a great solution, and questionably a turn-key solution, even > if you do something clever with configuration, but it gets things most of the > way there. > > Since this seems to be a big issue, as a recommend hosting "installs" on > trac-hacks, which would be aimed towards turn-key-ish installation > procedures. I'm imagining anything from the quick+dirty approach I show > above ("this is the install our organization uses. It aims to provide a trac > that....") to configurable and smart installers. I figure if there is as > much interest as there seems to be, then sharing our various methodologies > might eventually build to something (or some things, as the case may be) that > are of general use to many people. If there is enough interest, maybe an > "Install" section on trac-hacks might be a good idea. > > Any thoughts or interest? Its not my top priority, as my install procedure > worksforme, but if people think this is a good idea, I'm glad to codify my > rudimentary install for reference. > > Jeff Hammel > The Open Planning Project > http://topp.openplans.org > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
