-
Notifications
You must be signed in to change notification settings - Fork 182
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
docs(website): blog post about deploying to customer env #1452
base: main
Are you sure you want to change the base?
docs(website): blog post about deploying to customer env #1452
Conversation
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.
See inline comments. Overall great piece
|
||
- Use **multi-architecture Docker images** to support diverse systems. | ||
- Provide **metadata-rich Helm charts** with versioning and repository links for transparency. | ||
- Create clear templates for common deployment scenarios to minimize setup time. |
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 would rather call them examples in a documentation?
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.
You would call what exactly "examples"? I didn't fully get it
|
||
### Two Primary Approaches to Licensing | ||
|
||
1. **Simple On/Off Licensing**: |
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.
Often by giving access to the container registry
Newest blog post
π Description
β Checks
βΉ Additional Information