Skip to content

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

Draft
jwrosewell wants to merge 3 commits into
rcfrom
chore/configure-address
Draft

jwrosewell wants to merge 3 commits into
rcfrom
chore/configure-address

Conversation

@jwrosewell

@jwrosewell jwrosewell commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

The configuration page answers

The hold this draft opened with, "until https://51degrees.com/configure answers", is met. At 17:56 UTC on 13 November 2026 https://51degrees.com/configure answered 200 with the page "Cloud Configuration | 51Degrees", where it answered 404 at 14:20 UTC on 12 November. The old address still answers as well.

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.
  • 3 lines in 2 files changed (the comparison with rc shows 3 additions and 3 deletions in 2 files, over 2 commits).

pipeline-specification/features/properties.md gives the wording of two messages that every language's implementation shows. The language repositories carry the same change to their own messages.

Files and line counts
File Lines
device-detection-specification/required-examples.md 1
pipeline-specification/features/properties.md 2

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.

The two message wordings in pipeline-specification/features/properties.md now say "on the configuration page at". 51degrees-dotnet#142 carries the same wording in .NET's messages at its head aa8929da. Rust does not move yet. 51degrees-rust#392 at 1d62e5e2 keeps Rust's two messages in pipeline-engines/src/missing_property.rs as "in the configurator at https://configure.51degrees.com", because Rust's comparison with .NET checks those messages word for word, apart from the campaign tags, against the published .NET Pipeline 4.5.130, and moving them failed that comparison (run 43479753432). Rust's messages move once a .NET release with the new words reaches that comparison, which a follow-up issue in 51degrees-rust tracks. Until then Rust's messages differ from this page, and the old address still answers, so their link still works.

Each changed sentence
  • pipeline-specification/features/properties.md line 128: "...'. Check or create a resource key with the properties you need on the configuration page at https://51degrees.com/configure. | 0. Property n"
  • pipeline-specification/features/properties.md line 129: "...ded for your key under '{1}' are {2}. Check or change your key on the configuration page at https://51degrees.com/configure. | 0. Property name
    1."

Base branch

rc, because recent changes to this repository were merged into rc (for example #139 and #138) and reach main in a release pull request. On 13 November rc at 77dc1f6 was merged in with a merge commit, with no conflict.

Campaign tags

No campaign tag was added, removed or changed. The tagged link in device-detection-specification/required-examples.md keeps its five parameters, and the two addresses in pipeline-specification/features/properties.md stay untagged because .utm-lint.json excludes that file (it holds message wording, not links to follow).

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 3 lines in 2 files. 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.
  • After that merge, the same search on this branch at a667c4e finds none.
  • No build or test was run locally. The checks on this pull request run the campaign tag lint.
  • On the head, a667c4e, UTM link lint and Only rc into main passed.

The two checks before ready

  1. https://51degrees.com/configure loads, as above.
  2. A link with a sharing code and a query, https://51degrees.com/configure/jqz435Nc?utm_source=github&utm_medium=docs&utm_campaign=specifications&utm_content=device-detection-specification-required-examples.md&utm_term=cloud-device-detection, answered 200 with the same page at 17:56 UTC. The page reads the sharing code from its address and asks props/<code> for the properties to tick. https://51degrees.com/configure/props/jqz435Nc gives the same list as https://configure.51degrees.com/props/jqz435Nc, starting device.HardwareVendor device.JavascriptHardwareProfile. The page was not opened in a browser.

Merges with

The same move is a draft in each of these, and they merge together: .github#12, 51degrees-dotnet#142, 51degrees-go#114, 51degrees-java#115, 51degrees-nginx#476, 51degrees-node#87, 51degrees-php#77, 51degrees-python#107, 51degrees-rust#392, common-ci#318, documentation#311, pipeline-wordpress#88 and specifications#142.

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.
@jwrosewell jwrosewell changed the title Point Cloud Configurator links at 51degrees.com/configure Point configuration page links at 51degrees.com/configure Nov 12, 2026
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.
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