Skip to content

Point configuration page links at 51degrees.com/configure - #77

Merged
jwrosewell merged 3 commits into
rcfrom
chore/configure-address
Nov 13, 2026
Merged

jwrosewell merged 3 commits into
rcfrom
chore/configure-address

Conversation

@jwrosewell

@jwrosewell jwrosewell commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

The configuration page has moved to https://51degrees.com/configure, and the links and messages here still point at configure.51degrees.com.

The hold is met

This draft waited until https://51degrees.com/configure answered. At 17:33 and again at 22:23 UTC on 13 November, https://51degrees.com/configure, https://51degrees.com/configure/ and the coded links https://51degrees.com/configure/np5M4nlF and https://51degrees.com/configure/gGc3T5pT each answered 200 with the title "Cloud Configuration | 51Degrees". The old https://configure.51degrees.com/gGc3T5pT still answers 200 too, so nothing breaks for a reader who meets an old link.

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.
  • Only the address changed. No version number, workflow or other text was touched.
  • 36 lines in 24 files changed. The comparison with rc at a074012 shows 36 additions and 36 deletions in 24 files, after rc was merged in at 9c30dc3.

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 1
README.md 1
device-detection/cloud/examples/cloud/failureToMatch.php 3
device-detection/cloud/examples/cloud/gettingStartedConsole.php 1
device-detection/cloud/examples/cloud/gettingStartedWeb.php 1
device-detection/cloud/examples/cloud/metadataConsole.php 1
device-detection/cloud/examples/cloud/nativeModelLookupConsole.php 1
device-detection/cloud/examples/cloud/tacLookupConsole.php 1
device-detection/cloud/examples/cloud/userAgentClientHints-Web.php 3
device-detection/cloud/readme.md 1
device-detection/cloud/tests/classes/ResourceKeys.php 1
ip-intelligence/examples/cloud/getallproperties-console.php 1
ip-intelligence/examples/cloud/gettingstarted-console.php 1
ip-intelligence/examples/cloud/metadata-console.php 1
ip-intelligence/readme.md 1
location/examples/cloud/combiningservices.php 2
location/examples/cloud/configurefromfile.php 2
location/examples/cloud/gettingstarted.php 3
location/examples/cloud/webIntegration.php 1
location/examples/index.php 1
location/readme.md 1
location/tests/GeoLocationTests.php 1
pipeline/cloudrequestengine/src/Constants.php 1
pipeline/cloudrequestengine/tests/CloudRequestTests.php 5

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/cloud/examples/cloud/failureToMatch.php line 37: "* You can create a resource key using the 51Degrees configuration page."
  • device-detection/cloud/examples/cloud/userAgentClientHints-Web.php line 38: "* You can create a resource key using the 51Degrees configuration page."
  • device-detection/cloud/readme.md line 23: "configuration page, see our"
  • location/examples/cloud/combiningservices.php line 39: "* You can create a resource key using the 51Degrees configuration page."
  • location/examples/cloud/configurefromfile.php line 34: "* You can create a resource key using the 51Degrees configuration page."
  • location/examples/cloud/gettingstarted.php line 35: "* You can create a resource key using the 51Degrees configuration page."

Base branch

rc. rc at a074012f was merged in with a merge commit (9c30dc3). rc had added no new line with the old address since this branch was made, so the merge changed nothing here, and a search of the merged tree for configure.51degrees.com, ignoring case, finds none.

Releases

pipeline/cloudrequestengine/src/Constants.php is package code, so this change releases fiftyone.pipeline.cloudrequestengine. Under the release rule of #37 that also releases fiftyone.devicedetection and fiftyone.geolocation, which depend on it, and nothing else, because the other 23 files are Markdown, examples or tests.

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. The UTM link lint on this head passed.

How it was checked

  • A search of every file on rc for configure.51degrees.com, ignoring case, found 36 lines in 24 files. The same search on this head 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.
  • Full build run 43476001860, started with the shared draft build script on tmp/pr-matrix-77, passed on head 9c30dc3. All nine Setting 'PullRequestSha' lines name that head. The eight Build and Test jobs (Ubuntu PHP 7.4 to 8.5 and Windows PHP 8.3) passed, and Configure printed "Left out 5 macOS entries". 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 quick checks on this head (environment variable names, only rc into main, UTM link lint) passed.

What remains

  • No person has opened a coded link in a browser to see its properties ticked. The page is drawn in the browser, so a plain request shows the same page for every code, and that check needs a browser.

The Cloud Configurator has moved from configure.51degrees.com to
https://51degrees.com/configure. Links and mentions shown to people
(READMEs, comments, example output and messages) now use the new
address, keeping each link's key or sharing code and its query.
On the lines that carry the 51degrees.com/configure address, the text
people read now says "configuration page". Code identifiers, file
names and settings keys are unchanged.
@jwrosewell jwrosewell changed the title Point Cloud Configurator links at 51degrees.com/configure Point configuration page links at 51degrees.com/configure Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant