There is a script located at cloud/local/init.sh, that should start up a kind cluster.
The applications can be run in two modes, and the mode is set based on the spring profile used, cluster when running
inside the cluster, external when the app is running outside a cluster, in this case a .kubeconfig file needs to be
provided from the cluster to manage.
To configure it to run in a cluster the application requires cluster roles to be set up, take a look at cloud/local/development/rback and how the service account is set in deployment.
Start spring gradle app in development mode
bootRun --args='--spring.profiles.active=external' --continuous -xtest- continuous rebuild the app on change
- -xtest disabled the test from running every time
The ui is located in frontend
Start development mode:
pnpm devStart in production mode:
pnpm build
pnpm previewMain parts
The registry is hosted by itself inside the cluster
- Kind registry config loader
- containerd config
- Registry name resolution
- Static registry service cluster ip
- Data directory
Webdav is configured in cloud/local/development/webdav
Locally data would be stored in cloud/local/data/webdav
The resources defined in cloud/local/development/app/deploy.yaml are meant for development where you can start the application and access the api from outside of the cluster, when you make code changes it should automatically rebuild (because the code itself is mounted inside)
Container images are kept in the database.
For how to add new container images take a look at the data migration script
When it is added to the database the parameters are automatically picked up by the ui, no additional configuration should be necessary