-
Notifications
You must be signed in to change notification settings - Fork 80
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 developer quickstart guide for starting a local server #3382
Conversation
|
||
```shell | ||
./gradlew server-jetty-app:build | ||
./gradlew server-jetty-app:run -Pgroovy |
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.
Should mention that these commands are run from the root of the repo, not from this folder.
``` | ||
|
||
And then run via: | ||
This produces a more production-like environment. | ||
See [https://deephaven.io/core/docs/how-to-guides/configuration/native-application/](https://deephaven.io/core/docs/how-to-guides/configuration/native-application/) |
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.
Do these options not apply in the ./gradlew
scenario? Or should the link to this config info be under the Configuration
section below?
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.
It's "mostly" equivalent, but there may be differences. The big difference right now is EXTRA_CLASSPATH
is not supported.
The other environment variables, which are picked up at runtime, should work (DEEPHAVEN_APPLICATION
, DEEPHAVEN_DATA_DIR
, DEEPHAVEN_CACHE_DIR
, DEEPHAVEN_CONFIG_DIR
, and DEEPHAVEN_QUIET
).
No description provided.