The php scripts will reside on the phabricator host, no modifications to the apache config is needed. We won't need any dba assistance, chase already arranged for a user account with the minimal access to connect to the phabricator database and read the lookup tables. It's all self contained within phabricator. but I am about to submit a new diff that is production ready, that was just for testing. Is that Apache config / rewrite rules / PHP script already written and in git somewhere? It's going to be reading from a cross reference table in the phabricator-maniphest database, using the user account that already procured for this purpose. there is a backend DB used by those scripts that holds needed information? where is that database server? did you plan for it to be on localhost, on db1001, is it going to be mysql/mariadb or sqlite or ?.the scripts for this are PHP scripts on the phabricator instance.so the old Bugzilla box, zirconium doesn't get any traffic for anymore.No, there is a wildcard virtual host pointed to phabricator. have a new virtual host bugzilla.wm.org configured there that handles the redirects into phabricator.T366: Move Bugzilla to switch DNS over to point at the phabricator box itself T63: Phabricator requires a "real name" to register Mentioned Here T1198: Bugzilla HTML static version and database dump T111: Implement Wikimedia SUL in this Labs instance T232: MediaWiki login button has "" logo? T535: Document all the steps that need to be done during the Bugzilla migration T687: Convert Bugzilla's "Bug NNNNN" links to "TNNNNN" links in Phabricator T857: Imported bugs from bugzilla should be assigned the same number as their bugzilla ID (i.e. T882: Converted bugs could link to the original report in T1234: Restrict Bugzilla access to read-only T1358: Document what happens to bugzilla comment links T1199: Update links everywhere from Bugzilla to Phabricator T240: Map from bugzilla aliases to phabricator tasks Mentioned In T110622: Fix broken links to Bugzilla, especially from This also applies to Bugzilla's "saved searches" functionality - people will still be able to see and edit their search parameters in old-bugzilla and try to convert them manually into Phabricator. Queries for a specific status (open tickets) in some specific products/components are common but we won't have a mapping between Bugzilla products and components and Phab projects somewhere publicly stored, as URL parameters are fundamentally different in Phabricator. using buglist.cgi with a bug_id parameter plus a number of bug IDs with commata inbetween (to get a static list of tickets listed). More info, just for the records: Such URLs can have dozens of URL parameters, e.g. The banner ( T1234) will tell people that what they see is outdated. //(bugs|bugzilla)./buglist.cgi (always with additional URL parameters) will redirect to while keeping its URL parameters intact.///attachment.cgi (which can have additional URL parameters to ignore).Still possible to query for the attachment ID manually in Phabricator though.) ![]() //(bugs|bugzilla)./attachment.cgi?id=12345 (rather uncommon plus we won't keep the numbering scheme.//(bugs|bugzilla)./describecomponents.cgi (which can have additional URL parameters to ignore).//(bugs|bugzilla)./chart.cgi (which can have additional URL parameters to ignore).//(bugs|bugzilla)./report.cgi (which can have additional URL parameters to ignore).//(bugs|bugzilla)./reports.cgi (which can have additional URL parameters to ignore).//(bugs|bugzilla)./query.cgi (which can have additional URL parameters to ignore).//(bugs|bugzilla)./enter_bug.cgi (which can have additional URL parameters to ignore).Links that should go to the Phabricator homepage :.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |