On Wednesday, November 13, 2019 at 2:18:35 AM UTC-8, Velu Narasimman wrote: > > 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! >
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 - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/f06818d2-701f-4904-b8cc-2051939e0719%40googlegroups.com.
