Skip to content
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

Run-as-local-process and hot-reload development server #744

Closed
andrewazores opened this issue Nov 3, 2021 · 0 comments · Fixed by #745
Closed

Run-as-local-process and hot-reload development server #744

andrewazores opened this issue Nov 3, 2021 · 0 comments · Fixed by #745
Assignees
Labels
feat New feature or request

Comments

@andrewazores
Copy link
Member

Currently the intended development cycle for the Cryostat backend is to make edits to the sources, then run mvn verify to build the OCI image and run all relevant tests, then sh smoketest.sh to run that OCI image as a Podman container to test it manually with curl etc. This is a pretty long and slow process end-to-end. It can be sped up somewhat by doing mvn -DskipTests=true -Dcryostat.minimal=true package instead, to skip unit and integration tests and to not (re)build the web-client, but this is still fairly slow. It would be nice to have a devserver setup similar to what the web-client has, where changes cause automatic recompilation and redeploy, while the Cryostat backend webserver is running as a local JVM process on the development machine. There would be no sample apps available as in the smoketest.sh, and no ability to apply container resource limits, so it would not be a replacement for the existing development cycle. Rather it would be a nice-to-have when adding a new API handler or fixing a bug with an existing handler, for example, since changes could be much more rapidly made and verified using curl/httpie/wget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant