Hejsan, currently how one deploys DXR is somewhat up in the air. So let's get the pieces together. It's a little challenge to make this non-specific to the individual, so input from anyone who set up or will setup DXR is appreciated. I'm looking at Malini in particular here.
You find the script in my github: https://github.com/kalikiana/dxr/blob/update-sh/update.sh So update.sh has a couple of variables at the top. The idea is, you prepare this once. If you have multiple trees, there are 2 variables: ./update.sh or TREE=comm-central VCSPULL='echo .' ./update.sh VCSPULL is the command updating the source, or doing nothing. I also included the typical error checks. So if you pipe this to a log file that should save some time being puzzled. If you specify REMOTE, rsync will copy to your web frontend server assuming the file layout is the exact same. To make sure you don't get surprises I have a patch waiting for review, to version the databases. Ehsan, could you look into that, please? https://bugzilla.mozilla.org/show_bug.cgi?id=708588 And some cleaning up for the layout: https://bugzilla.mozilla.org/show_bug.cgi?id=708600 https://bugzilla.mozilla.org/show_bug.cgi?id=708589 Originally I was going to literally tear apart the modules, see the branch I pushed earlier. You would have the indexer, the HTML generator and the search frontend split. But it turns out, that would be a pain to maintain for plugin writers. So I figure mirroring the folder layout and wasting a few bytes, which is hot air compared to the actual data, is eventually more useful. Feedback still welcome of course. If I'm assuming too much to my specific setup, please point it out. ciao, Christian _______________________________________________ dev-static-analysis mailing list [email protected] https://lists.mozilla.org/listinfo/dev-static-analysis
