On Thu, May 14, 2015 at 5:09 PM, Rick Macdonald <[email protected]> wrote:
> > The instructions also say the following: > > >> Alternatively to aliasing /trac/chrome/common, you can tell Trac to >> generate direct links for those static resources (and only those), using >> the [trac] htdocs_location >> <http://trac.edgewall.org/wiki/TracIni#trac-section> configuration >> setting: >> >> [trac]htdocs_location = http://static.example.org/trac-common/ >> >> Note that this makes it easy to have a dedicated domain serve those >> static resources, preferentially ​cookie-less >> <http://code.google.com/speed/page-speed/docs/request.html#ServeFromCookielessDomain>. >> >> > and I do in fact have htdocs_location = http://my.example.org/trac/htdocs > . Do I read the above right that this accomplishes the same thing? (I don't > understand the bit about "cookie-less"). > Sorry for the delay. Yes, using htdocs_location should accomplish the same thing as aliasing /trac/chrome/common. It should work fine provided you don't have any plugin, site or shared static assets. Basically, htdocs_location accomplishes the same thing as aliasing if you are just running stock Trac. If you have some customization or plugins, then there are additional things to alias, in which case you may not want to use htdocs_location, because you'll need aliasing directives as well anyway. I actually think that's all fairly confusing, and I'm going to investigate whether we can make htdocs_location as flexible as aliasing in a future Trac release. - 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
