generated from camunda-community-hub/zeebe-worker-java-template
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
First version for the developer to develop Cherry
- Loading branch information
1 parent
1cc66d9
commit ba2d8f0
Showing
3 changed files
with
48 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
# Cherry Developer | ||
The purpose of the document is to expalin how to develop and publish Cherry | ||
|
||
|
||
# Running locally | ||
To run locally the runtime, in Intellij for example, check the different topics | ||
|
||
## Configuration | ||
In local, you can use a H2 or a Postgres database. | ||
By default, [application.yaml](../../src/main/resources/application.yaml) use an H2 database. | ||
To use a Postgres database, use the [application-postgres.yaml](../../src/main/resources/application-postgres.yaml) | ||
|
||
In Intellij, use `--spring.profiles.active=postgres` | ||
|
||
## Start the runtime | ||
Execute `io.camunda.CherryApplication` | ||
|
||
![IntellijConfiguration.png](IntellijConfiguration.png) | ||
|
||
## Debug the UI | ||
To debug the UI, the React part can be start via npm | ||
|
||
```shell | ||
cd src/main/frontend | ||
npm start | ||
``` | ||
|
||
|
||
# Build the docker image | ||
|
||
Use the command (replace the version by the correct one) | ||
```shell | ||
docker build -t ghcr.io/camunda-community-hub/zeebe-cherry-runtime:3.1.2 . | ||
``` | ||
|
||
A new image is build. Push the image, and tag it with the `lastest` | ||
|
||
```shell | ||
docker tag ghcr.io/camunda-community-hub/zeebe-cherry-runtime:3.1.2 ghcr.io/camunda-community-hub/zeebe-cherry-runtime:latest | ||
docker push ghcr.io/camunda-community-hub/zeebe-cherry-runtime:3.1.2 | ||
docker push ghcr.io/camunda-community-hub/zeebe-cherry-runtime:latest | ||
``` | ||
|
||
Go to https://github.com/camunda-community-hub/zeebe-cherry-runtime/pkgs/container/zeebe-cherry-runtime and check that the last image is correctly updated | ||
![GitHub Package page.png](GitHubPackage.png) | ||
|
||
|
||
|