On Thu, May 14, 2015 at 2:40 PM, Rick Macdonald <[email protected]> wrote:
> > 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, > The trac.fcgi that is created is suitable for most users. You are likely using a copy of this to serve your site. Your copy may have been tweaked after generating it with deploy. > 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? > I suggest instead that you should remove the 1.0.2 files from "site" and then rerun deploy. The "site" directory in your environment is only for site customization files. You likely have no site customization, in which case it *should* be empty. "deploy" will extract the necessary files and put them in the location you specify, which is wherever your web server is configured to serve static assets from. It's possible that whoever configured your site is abusing the environment htdocs directory by serving the static assets from that directory. If you are able to share the contents of .htaccess we can probably sort that out. > 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? > Well, I'm not sure since I haven't seen your .htaccess rewrite rules. However, you are probably okay with [trac] htdocs_location having been configured. > And if that's the case, it seems confusing to have the 1.0.2 htdocs in the > "site" directory. > Right, that's not the proper location to serve htdocs from. The environment htdocs directory is for site customization files. The typical scenario is to run: trac-admin tracenv deploy www and then point the web server configuration to serve files from www/htdocs Currently, I'm quite sure the files in trac/htdocs are being used. Does > getting them into the static assets setup improve performance? > Having them served by the web server improves performance. trac-admin deploy is just a tool to extract all your files to a directory that you can serve. You should be able to delete the files and rerun deploy at any time to regenerate the directory. In fact, that is a necessary step for upgrading Trac: http://trac.edgewall.org/wiki/TracUpgrade#a5.Refreshstaticresources > Sorry that I'm so lame about all this... > Don't feel bad, there is much room for improvement in our documentation, and I think you have a complex setup that was generated by someone else. Hope you are having better luck recently. Please let us know if you have any additional trouble. - 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.
