Those are the instructions that confuse me. I ran the deploy, pointing it to /tmp to see what it would do. It created a cgi-bin directory with trac.fcgi that I don't think I want or need, and it created htdocs. The htdocs dir has my old 1.0.2 files in "site", and "common" contains the new 1.0.3 files. I think I need to copy these to my existing trac/htdocs to replace the 1.0.2 files?
What confuses me is what good does the deploy do if I can't add the /trac/chrome aliases to the apache config? Or, are the .htaccess Rewrites taking care of this for me? And if that's the case, it seems confusing to have the 1.0.2 htdocs in the "site" directory. Currently, I'm quite sure the files in trac/htdocs are being used. Does getting them into the static assets setup improve performance? Sorry that I'm so lame about all this... - Rick -- 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.
