-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow self-hosting of custom site-specific user and operator documentation #200
base: devel
Are you sure you want to change the base?
Conversation
@@ -3,7 +3,7 @@ | |||
collections: | |||
- name: https://github.com/azimuth-cloud/ansible-collection-azimuth-ops.git | |||
type: git | |||
version: 0.13.2 | |||
version: feat/mkdocs # 0.13.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: Revert this before merging.
As part of the standard Azimuth deployment procedure, a copy of the generic user and operator | ||
documentation sites are published on separate subdomains of the Azimuth ingress URL. For an Azimuth | ||
instance hosted at `portal.azimuth.example.com`, the documentation can be accessed at | ||
`user.docs.azimuth.example.com` and `admin.docs.azimuth.example.com` respectively. The operator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to use operator.docs.azimuth.example.com instead of admin.docs.azimuth.example.com? Would match how it's being referred to in this section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah probably, I flip-flopped between admin and operator a few times while putting this together. I guess we should settle on one or the other for consistency before finalising the changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fact, that's a mistake in the docs because I also changed my mind and went for user-guide
and admin-guide
as the subdomains after writing those docs 🤦
This PR adds the ability to build and publish the Azimuth user documentation on a subdomain of the main Azimuth URL.
It depends on azimuth-cloud/ansible-collection-azimuth-ops#732 which in turn makes use of https://github.com/azimuth-cloud/mkdocs-helm to build and publish the documentation sites.