DOC-3535 - Standardize on-premises registry login and support references#4218
Merged
Conversation
…eferences
Align all on-premises container registry login examples with the published
pattern used across the service pages (Export to PDF, Spelling, Hyperlinking,
Image Proxy, Import/Export Word):
- Replace the remaining `<registry-username>` placeholders with the username
`tiny` on the AI on-premises production page (Podman login and the
`kubectl create secret docker-registry` example).
- Use `docker login -u tiny -p [access-token] registry.containers.tiny.cloud`
(and the Podman equivalent) consistently on the AI on-premises getting
started and production pages, and refer to the credential as an access token.
- Replace the hardcoded `support@tiny.cloud` email on the AI on-premises
getting started and troubleshooting pages with the standard
`link:{supporturl}/[{supportname}]` reference.
metricjs
approved these changes
Jun 16, 2026
tiny-ben-tran
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket: DOC-3535
Site: Staging branch
Changes:
tinymceai-on-premises-production.adoc— replaced the remaining<registry-username>placeholders with the usernametinyin the Podman login and thekubectl create secret docker-registryexample.tinymceai-on-premises-getting-started.adocandtinymceai-on-premises-production.adoc— usedocker login -u tiny -p [access-token] registry.containers.tiny.cloud(and the Podman equivalent) consistently, and refer to the credential as an access token.tinymceai-on-premises-getting-started.adocandtinymceai-on-premises-troubleshooting.adoc— replaced the hardcodedsupport@tiny.cloudemail with the standardlink:{supporturl}/[{supportname}]reference.Background: follow-up to DOC-3530, which fixed only the getting-started page. This brings the rest of the on-premises pages in line so the registry username (
tiny) and access-token terminology are consistent everywhere.Prepared for documentation team review.