Should I run the "deploy" command for all projects(environments)?

17 views

Skip to first unread message

Velu Narasimman

unread,

Nov 13, 2019, 5:18:35 AM11/13/19

to Trac Users

Hi,

In my implementation of Trac, I have a lot of projects at the path /opt/Projects/. There would be roughly 1000 projects (or environments) available under the path /opt/Projects. From the static resource mapping page here https://trac.edgewall.org/wiki/TracInstall#MappingStaticResources it is advised to run the deploy command

$ trac-admin /var/trac/<project> deploy /var/www

So does that mean I should run this above command for all those 1000 projects manually? or is it enough to run this command for just one project? I ran it for 20 projects and what I observe is the same action is repeated for those projects - extracting all the css, js, images, fonts and other static files from all my plugins into the new location say, /var/www.

Is it enough to run this command for a single project? Please guide me.

Thanks in advance!

RjOllos

unread,

Nov 13, 2019, 11:49:08 AM11/13/19

to Trac Users

If all of your projects are using the same Trac installation via a shared Python environment or virtual environment, and all of your plugins are installed globally, then you can run "deploy" just once and all Trac environments can shared the extracted resources. The resources are mapped through Alias directives in the web server configuration: https://trac.edgewall.org/wiki/TracInstall#MappingStaticResources