There are three possible choices for the default value of Config.wooBugURL: 1. "php/starcomment.php" 2. "http://brasstacks.mozilla.com/starcomment.php" 3. "http://tbpl.mozilla.org/php/starcomment.php" Choice 1 has the disadvantage of only working on exactly one server: tbpl.mozilla.org. That's because the server needs access to elasticsearch1.metrics.sjc1.mozilla.com, and normal servers don't have that. (tbpl.mozilla.org got it in bug 638515.) Choice 2 has the advantage of working from every server, but might not be as reliable, as Jonathan says in bug 601743 comment 24: (In reply to comment #24) > Only that brasstacks is probably not quite as reliable as the tbpl machine; > it's sort of a sandbox for a lot of automation tools, and the webserver > sometimes gets restarted, etc. It would also make the local starcomment.php file unnecessary, unless we changed Config.wooBugURL to "php/starcomment.php" only on tbpl.mozilla.org and merged with repo changes on every deployment. Choice 3 looks like a good way out.

Comment on attachment 543608 [details] [diff] [review] v1 Review of attachment 543608 [details] [diff] [review]: ----------------------------------------------------------------- As discussed in icq: Is the script on tbpl.mozilla.org really allowed to write to the woo database? Need to verify that first.

We can do that when we deploy it, and back it out if it doesn't work.

Seems to have worked out in the end.