-
Notifications
You must be signed in to change notification settings - Fork 189
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
[draft] ec2 architecture and guide #4585
base: main
Are you sure you want to change the base?
Conversation
👋 🤖 🤔 Hello, @Langleu! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
@theburi and @conceptualshark maybe you could have a look over this next week and give some general feedback on maybe what you're missing and still expecting to see. I was going in the direction of GitLab's approach on the topic just that we don't have any benchmarks to guide (which I don't see happening anytime soon). Essentially, on a high level talking about the idea of Reference Architectures, actual architecture, and guiding customers along to choose their path based on
Current pages: I'm on a team event next week + RSG, so take your 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.
This is a good start. Lets discuss few topics as I was reading this guide:
- Adding Architecture tech spec, overview page that just lists facts
- Can we include full production configuration in a single page, including TLS, Auth and connectivity? Or shall we make it a multi-step guide: install foundation, then add security, then add connectivity.
- I feel like we need to add a bit more description to each step to describe what is going on.
Since the previous links were moved: |
|
||
## Support Considerations | ||
|
||
We recognize that deviations from the reference architecture are unavoidable. However, such changes will introduce additional complexity, making troubleshooting more difficult. When modifications are required, ensure they are well-documented to facilitate future maintenance and support more quickly. Camunda publishes [supported environments](/docs/reference/supported-environments/) information to help you navigate supported configurations. |
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.
[docsInstance.hrefDocsToDocs] Improper link format: 'supported environments'. Please specify the file extension.
docs/self-managed/reference-architecture/reference-architecture.md
Outdated
Show resolved
Hide resolved
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.
Rock solid documentation! Wp
I left some comments
docs/self-managed/reference-architecture/reference-architecture.md
Outdated
Show resolved
Hide resolved
@@ -1567,5 +1567,16 @@ module.exports = { | |||
}, | |||
], | |||
}, | |||
{ | |||
"Reference Architecture": [ |
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.
We could have the RA part of the Setup section, for existing docs such as gitlab, it's part of the Install chapter
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 had it previously but talked with Andrey about it, the idea is to have it more prominently as guidance in the future.
Not sure how long setup
will continue existing as is.
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'd keep the Reference Arch structure wise as is for now, we can still move it till 8.7 depending on feedback.
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.
The only issue I see with that is the fact that this category is not self-describing.
Setup / Installation are simple words
Reference Arch needs its own definition
I don't have strong opinion on that, maybe @conceptualshark you have one regarding the developer experience of those words
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.
@theburi maybe also of interest to you
docs/self-managed/reference-architecture/manual/manual-overview.md
Outdated
Show resolved
Hide resolved
docs/self-managed/reference-architecture/manual/manual-overview.md
Outdated
Show resolved
Hide resolved
docs/self-managed/reference-architecture/manual/manual-overview.md
Outdated
Show resolved
Hide resolved
docs/self-managed/reference-architecture/reference-architecture.md
Outdated
Show resolved
Hide resolved
docs/self-managed/reference-architecture/reference-architecture.md
Outdated
Show resolved
Hide resolved
@conceptualshark I can't request you as reviewer but would be good to have it reviewed from your side. |
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.
LGTM! Only the sidebar structure that is a remaining point.
Very well done :)
The preview environment relating to the commit f6d461e has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4585/index.html |
Description
Draft/WIP PR to explore changes and content movement in the preview.
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).