-
Notifications
You must be signed in to change notification settings - Fork 188
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
add C8Run documentation to self managed #4266
Conversation
👋 🤖 🤔 Hello! 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.5/.
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. |
@conceptualshark I wasn't sure if you needed this reviewed, but I will just in case 👍 |
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 - great work! Just some non-blocking comments to consider 👍
2. Navigate to the new C8Run directory. | ||
3. Start C8Run by running `./start.sh` (or `.\c8run.exe start` on Windows) in your terminal. | ||
|
||
When successful, a new Operate window will open automatically. |
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.
When successful, a new Operate window will open automatically. | |
When successful, a new Operate window automatically opens. |
NB suggestion
When successful, a new Operate window will open automatically. | ||
|
||
:::note | ||
If C8Run fails to start, run the [shutdown script](/self-managed/setup/deploy/local/c8run.md/#shut-down-c8run) to end the current processes before running the start script again. |
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.
If C8Run fails to start, run the [shutdown script](/self-managed/setup/deploy/local/c8run.md/#shut-down-c8run) to end the current processes before running the start script again. | |
If C8Run fails to start, run the [shutdown script](/self-managed/setup/deploy/local/c8run.md/#shut-down-c8run) to end the current processes, and run the start script again. |
NB suggestion
C8Run is not supported for production use. | ||
::: | ||
|
||
The Camunda 8 Run Distribution, or C8Run, allows you to set up a local installation environment of Camunda 8 via a downloadable script. This page guides you through the manual installation of the Camunda 8 on a local or virtual machine. |
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 Camunda 8 Run Distribution, or C8Run, allows you to set up a local installation environment of Camunda 8 via a downloadable script. This page guides you through the manual installation of the Camunda 8 on a local or virtual machine. | |
You can use the Camunda 8 Run Distribution (C8Run) to set up a local installation environment of Camunda 8 via a downloadable script. This page guides you through the manual installation of the Camunda 8 Run Distribution on a local or virtual machine. |
NB suggestion
## Install and start C8Run | ||
|
||
1. Download the [latest release of C8run](https://github.com/camunda/camunda/releases/tag/c8run-8.6.0-alpha3) for your operating system and architecture. Opening the .tgz file will extract the C8Run script into a new directory. | ||
2. Navigate to the new C8Run directory. | ||
3. Start C8Run by running `./start.sh` (or `.\c8run.exe start` on Windows) in your terminal. | ||
|
||
When successful, a new Operate window will open automatically. | ||
|
||
:::note | ||
If C8Run fails to start, run the [shutdown script](#shut-down-c8run) to end the current processes before running the start script again. | ||
::: |
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 previous comments
|
||
## Access Camunda components | ||
|
||
All C8Run components can be accessed with the username/password combination `demo`/`demo`. |
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.
All C8Run components can be accessed with the username/password combination `demo`/`demo`. | |
All C8Run components can be accessed using the username/password combination `demo`/`demo`. |
- Tasklist: `http://localhost:8080/tasklist` | ||
- Operate: `http://localhost:8080/operate` | ||
|
||
The following components do not have a web interface, but the URLs may be required for any additional configuration: |
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 following components do not have a web interface, but the URLs may be required for any additional configuration: | |
The following components do not have a web interface, but the URLs may be required for additional configuration: |
- **Cluster endpoint:** `http://localhost:26500`, the location of your Zeebe Gateway | ||
- **Authentication:** None | ||
|
||
A success notification will display when complete. [Start a new process instance](/components/modeler/desktop-modeler/start-instance.md) to view your running process in Operate. |
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.
A success notification will display when complete. [Start a new process instance](/components/modeler/desktop-modeler/start-instance.md) to view your running process in Operate. | |
A success notification is shown when deployment is complete. [Start a new process instance](/components/modeler/desktop-modeler/start-instance.md) to view your running process in Operate. |
@@ -0,0 +1,90 @@ | |||
--- | |||
id: c8run | |||
title: "Local installation with C8Run" |
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.
Can we use Camunda 8 Run (C8Run). C8Run looks like an abbreviation. It will also help with SEO.
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.
Late to the party 💃 but here I am!! 😆
Can we use Camunda 8 Run (C8Run). C8Run looks like an abbreviation. It will also help with SEO.
@conceptualshark you can consider using keywords
in the page metadata for things like this.
keywords: ["C8Run"]
f482daf
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.
New changes all lgtm - great job - approved 👍
🧹 Preview environment for this PR has been torn down. |
|
||
1. Download the [latest release of Camunda 8 Run](https://github.com/camunda/camunda/releases/tag/c8run-8.6.0-alpha3) for your operating system and architecture. Opening the .tgz file extracts the Camunda 8 Run script into a new directory. | ||
2. Navigate to the new `c8run` directory. | ||
3. Start Camunda 8 Run by running `./start.sh` (or `.\c8run.exe start` on Windows) in your terminal. |
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 assume ./start.sh
will work for both Linux and Mac users?
Description
Product Hub link: https://github.com/camunda/product-hub/issues/2240
Adds the feature documentation for C8Run to the Self Managed docs. Does not include the getting started experience as part of this update (though the reusable component has been created for later implementation).
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).