[jwrosewell]

The new address answers

This draft was to wait until https://51degrees.com/configure answers. At 17:35 UTC on 13 November it does. /configure, /configure/, /configure/gGc3T5pT and /configure?utm_source=code each answer 200 with the page title "Cloud Configuration | 51Degrees", the same title configure.51degrees.com serves, and the page at the new address loads the configuration app with <base href="/configure/">. On 13 November at 15:01 the same addresses answered 404.

What changed and why

The configuration page has moved from configure.51degrees.com to https://51degrees.com/configure. The links and mentions that people read (READMEs, code comments, example output, and the messages that tell someone where to create a Resource Key) now use the new address.

• https://configure.51degrees.com/<code>?<query> became https://51degrees.com/configure/<code>?<query>, with each key, sharing code, path, trailing slash and query kept exactly as written.
• The address changed, and where a message called the page "configurator" it now says "configuration page", as the Wording section below lists. No version number or workflow was touched.
• 61 lines in 35 files changed (the comparison with rc shows 61 additions and 61 deletions in 35 files, over 3 commits and two merges of rc). The 61st is the escaped-dot pattern in location/examples/examples.test.js line 44, which 74a087a changes.

The occurrences in code are constants and strings that are only written into messages telling a person where to create a Resource Key (the cloud request engine's error messages, the examples' output, and the test helpers that explain a missing key).

Files and line counts

File	Lines
AGENTS.md	2
README.md	1
device-detection/fiftyone.devicedetection.cloud/examples/cloud/configurator-console/configurator.js	2
device-detection/fiftyone.devicedetection.cloud/examples/cloud/gettingstarted-console/gettingStarted.js	2
device-detection/fiftyone.devicedetection.cloud/examples/cloud/gettingstarted-web/gettingStarted.js	2
device-detection/fiftyone.devicedetection.cloud/examples/cloud/metadata-console/metaData.js	1
device-detection/fiftyone.devicedetection.cloud/examples/cloud/nativemodellookup-console/nativeModelLookup.js	1
device-detection/fiftyone.devicedetection.cloud/examples/cloud/taclookup-console/tacLookup.js	1
device-detection/fiftyone.devicedetection.cloud/examples/cloud/useragentclienthints-web/userAgentClientHintsWeb.js	2
device-detection/fiftyone.devicedetection.cloud/readme.md	1
device-detection/fiftyone.devicedetection.shared/lib/keyUtils.js	1
device-detection/fiftyone.devicedetection/examples/gettingStarted.js	2
device-detection/fiftyone.devicedetection/readme.md	1
device-detection/readme.md	4
ip-intelligence/fiftyone.ipintelligence.cloud/examples/cloud/getallproperties-console/getAllProperties.js	2
ip-intelligence/fiftyone.ipintelligence.cloud/examples/cloud/gettingstarted-console/gettingStarted.js	2
ip-intelligence/fiftyone.ipintelligence.cloud/examples/cloud/gettingstarted-web/gettingStarted.js	2
ip-intelligence/fiftyone.ipintelligence.cloud/examples/cloud/metadata-console/metaData.js	2
ip-intelligence/fiftyone.ipintelligence.cloud/examples/cloud/mixed/gettingstarted-console/gettingStarted.js	2
ip-intelligence/fiftyone.ipintelligence.cloud/examples/cloud/mixed/gettingstarted-web/gettingStarted.js	2
ip-intelligence/fiftyone.ipintelligence.cloud/readme.md	1
ip-intelligence/fiftyone.ipintelligence.shared/lib/keyUtils.js	1
ip-intelligence/fiftyone.ipintelligence/examples/gettingStarted.js	2
ip-intelligence/fiftyone.ipintelligence/readme.md	1
ip-intelligence/readme.md	4
location/examples/combiningServices.js	3
location/examples/configureFromFile.js	2
location/examples/examples.test.js	1
location/examples/gettingStarted.js	3
location/examples/webIntegration.js	3
location/tests/geoLocationCloud.test.js	1
pipeline/fiftyone.pipeline.cloudrequestengine/errorMessages.js	1
pipeline/fiftyone.pipeline.cloudrequestengine/readme.md	1
pipeline/fiftyone.pipeline.cloudrequestengine/tests/liveCloudKeys.js	1
pipeline/fiftyone.pipeline.did/tests/liveCloudKeys.js	1

Wording

On the lines that carry the address, the text people read now calls the place the "configuration page". Code identifiers, file and folder names, settings keys and documentation page addresses are unchanged. Other lines that use the old name were left for a separate sweep.

Each changed sentence

• device-detection/fiftyone.devicedetection.cloud/examples/cloud/configurator-console/configurator.js line 24: "* This example is displayed at the end of the configuration page"
• device-detection/fiftyone.devicedetection.cloud/readme.md line 53: "...le for cloud tests. You can obtain a resource key from the 51Degrees configuration page and assign it to the e"
• device-detection/fiftyone.devicedetection/readme.md line 48: "You need to obtain a 51Degrees cloud resource key from the 51Degrees configuration page and assign it to the e"
• device-detection/readme.md line 40: "configuration page, see our"
• device-detection/readme.md line 202: "...le for cloud tests. You can obtain a resource key from the 51Degrees configuration page and assign it to the e"
• ip-intelligence/fiftyone.ipintelligence.cloud/readme.md line 14: "...tain one covering everything the examples display from the 51Degrees configuration page with a paid su"
• ip-intelligence/fiftyone.ipintelligence/readme.md line 14: "...g everything the examples display can be obtained from the 51Degrees configuration page with a paid su"
• ip-intelligence/readme.md line 38: "configuration page, see our"
• ip-intelligence/readme.md line 45: "this link."
• ip-intelligence/readme.md line 52: "this link."
• ip-intelligence/readme.md line 203: "...urce key covering everything the examples display from the 51Degrees configuration page and assign it "
• location/examples/combiningServices.js line 38: "You can create a resource key using the 51Degrees configuration page."
• location/examples/configureFromFile.js line 38: "configuration page."
• location/examples/gettingStarted.js line 35: "You can create a resource key using the 51Degrees configuration page."

Base branch

rc, because recent changes to this repository were merged into rc (for example #84 and #82) and reach main in a release pull request.

Campaign tags

No campaign tag was added, removed or changed. The shared campaign tag lint (scripts/utm-lint.ps1 in common-ci) applies the same rules to configure.51degrees.com and 51degrees.com, so every link that was tagged keeps its five parameters and every link that was untagged was in a file the lint does not check (test folders) and stays untagged.

What was left alone

Nothing. No occurrence of the old address remains on this branch.

How it was checked

• A search of every file on rc for configure.51degrees.com, ignoring case, found 60 lines in 34 files when this was written. After 68684780, which merges rc at 24592ac with no conflict, the same search on this branch finds none.
• Each occurrence outside Markdown and comments was read in place to confirm it is text shown to a person and not a value the code calls or compares against a reply from the cloud service.
• Build 43567933316 on tmp/pr-matrix-87-mon2, on the head 752bfe2, passed. All seven Setting 'PullRequestSha' lines are 752bfe2, Configure printed "Left out 2 macOS entries", and each of the six Ubuntu, Ubuntu ARM and Windows jobs on Node 22 and 24 ran 1,383 unit tests passed with 2 skipped, and 133 integration tests passed with 4 skipped. macOS was left out of this draft's full build under the 9 November decision. The rc head is built with macOS before it merges into main. The earlier build 43477197935 on 6868478 passed as well.

The merges of rc

• cc7aa39f merges rc with #95, which also changed four location examples. combiningServices.js and gettingStarted.js conflicted, and each is resolved to rc's code with the new address. 74a087aa changes location/examples/examples.test.js line 44, which expected the old address written with escaped dots, so a search for the plain address had missed it.
• 752bfe29 merges rc at fe81e01, which holds #37. Give each package its own version and release only what changed #37 moved the shared packages' code from tests to lib and left a one-line re-export at each old path, so the two conflicts, each package's tests/keyUtils.js, are resolved to rc's re-export, and the address changes in lib/keyUtils.js of both shared packages instead. A search of the branch for configure.51degrees.com, ignoring case, finds nothing, and the shared campaign tag lint passes.

Nothing else needs to merge first.

Before marking ready

1. Confirm https://51degrees.com/configure loads. Done, as above.
2. Confirm that a link with a sharing code and a query, such as one of the changed links, opens with its properties ticked. Done in the review of 13 November at about 22:40 UTC, which found that the new app reads the sharing code from the path, and that /configure/props/ at the new address returns the same property lists as the old host.