With this configuration, you can use the ent cli (https://dev.entando.org/next/docs/reference/entando-cli.html) to perform the full deployment sequence:
- Prepare the bundle directory:
cp -r bundle_src bundle - Initialize the project:
ent prj init - Initialize publication:
ent prj pbs-init(requires the git bundle repo url) - Attach to kubernetes for an Entando application via ent attach-kubeconfig config-file or similar
- Build:
ent prj build(build the frontend and backend) orent prj fe-build -a(to just build the frontend, including changes from bundle_src) - Build for configuration widgets:
ent prj fband choose config widget number - Publish:
ent prj pbs-publish(publish all) - Deploy (after connecting to k8s above):
ent prj deploy - Install the bundle via 1) App Builder, 2)
ent prj install, or 3)ent prj install --conflict-strategy=OVERRIDEon subsequent installs. - Iterate steps 1-4 to publish new versions.
You can use the following commands from the application folder to run the local stack
ent prj xk start- or stop to shutdown keycloak again.ent prj be-test-run- to run the microserviceent prj fe-test-run- to run the React frontend
- Access Keycloak at http://localhost:9080/auth/
- Access Springboot at http://localhost:8081/swagger-ui.html
- Use client web_app when authorizing the microservices
- only admin role is required to run the template service