> Doing the pip first worked, though I had to lengthen the timeout delay. This > machine sits behind a firewall that actually downloads everything on your > behalf first, then scans it for viruses/issues, then returns it to you if it > passes all checks.
Ooo, fancy-pants. :-) > Rebuild worked just fine. Good! > virtualenv is kind of cool; may have to learn a bit more about that. Yep, I don't do anything without that, lest I muck up my global environment and then wonder why everything on my box acts weirdly from then on. > Is the vagrant setup that included able to set up a complete environment in a > virtual machine such that I wouldn't have to configure my personal desktop > (or some other server) to be the DXR server? I didn't really intend the VM to act as a production server, but I don't see any hard-and-fast reason that it couldn't. The Apache config is fine, and if it doesn't suit your needs, it's at least a good example. > Two other issues: > > 1. callers:someFunc never completes for me; I get a "504 Gateway Timed Out" > Is there an easy way to run the same dxr request from the command line to see > if it's a timeout problem or a query issue? actually, is there a CLI-level > interface at all? Are you accessing DXR through Apache, then? I think if you run the dev server with dxr-serve.py and talk straight to it, it won't time out. It sounds like we're missing an index or something. > 2. when dxr-build finishes generating the files/directory hierarchy into > 'target_folder', it doesn't put any of the .htaccess files in there. I have > to copy them over from my previous target directory. Should they be > generated into there, or should I expect to have to replenish them anew each > time? We don't bother with htaccess files anymore. Static files are no longer served directly by Apache, as I found that it didn't make enough of a speed difference to matter. See the comments in httpd/conf.d/dxr.conf: # We used to make special efforts to also serve the static pages of # HTML-formatted source code from the tree via plain Apache, but that # tangle of RewriteRules saved us only about 20ms per request. You can do # it if you're on a woefully underpowered machine, but I'm not maintaining # it. > 3. I also find that the .htaccess files that are part of the distribution are > insufficient with regard to Options required. I need both ExecCGI and > FollowSymLinks in order for it to work. That might be a consequence of my > apache config, but even so it might be worthwhile to add that Options line > into the boilerplate dot-htaccess and just comment it out by default. I assume you're talking about the old htaccess files you pulled from the old build. There shouldn't be any anymore. You can take all those fancy RewriteRules out of your Apache config. _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
