On 26 Aug, 04:38, sam <[email protected]> wrote: > Hi All, > > I found the documentation in the deploy for multiple projects > (http://trac.edgewall.org/wiki/TracInstall#DeployingTrac) a bit confusing: > > trac-admin deploy requires an existing env to work. This suggests that the > deploy is somehow w.r.t. that env. Yet the way to deploy trac for multiple > envs is(/seems to be) to do one of these deploys w.r.t. to a given env, > then tweak the resulting trac.(f,s)cgi script correct? > > What is being got from that particular env if anything? Is this just a > limitation/bug of the command line parser? >
Nope. Extracting resources will extract from both Trac itself and from any plugins enabled for the environment, as well as the project htdocs directory (virtual 'site' directory). Discovering the full range of plugins and locations for extraction requires loading environment, loading configuration, loading plugins and calling the plugins using a real environment instance. Faking an environment will only allow us to extract the chrome/common resources, and scripts would be useless as they cannot point to an actual working location. Note that deploying is just a helper tool for you, not something that is required to configure or go live with a project. If you have 10 projects with same code/plugins, you may only need to deploy once and tweak scripts and settings to suite your need. :::simon https://www.coderesort.com Additionally, the actual extraction happens using the Trac plugin API and calling any Trac plugin is also something that -- You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en.
