You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24-64Lines changed: 24 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,42 +171,10 @@ upper right corner.  with [deephaven-ib](https://github.com/deephaven-examples/deephaven-ib)
172
172
installed. The launch can either happen via a local installation or via Docker images.
173
173
174
-
Lightweight installations use pip-installed Deephaven. These systems have less overhead, but they lack
175
-
a few Deephaven IDE features. Heavyweight installations launch the entire [Deephaven](https://deephaven.io) system.
176
-
These systems launch multiple Docker containers and have more overhead, but they provide all Deephaven IDE features.
174
+
For a Docker Compose example, see [docker/release/](docker/release/).
177
175
178
-
If you are running scripts that do not need human interaction, consider using a pip-installed option.
179
-
If you are interactively working with data, consider the full deephaven system.
180
176
181
-
### (Option 1) Launch the full Deephaven system -- interactive
182
-
183
-
> **_NOTE:_** Deephaven does not yet have published Docker images for all architectures. This launch should work on Linux (AMD64 and ARM64), Mac (Intel), and Windows WSL. It is not yet supported on Windows without WSL or Mac (M1 and M2). In these cases, the `full_web_1` Docker image will exit. This can be seen using `docker ps` or `docker compose ps`. For these architectures, you will need to build Deephaven Docker images locally. See [Build and launch from source](https://deephaven.io/core/docs/how-to-guides/launch-build/).
184
-
185
-
186
-
The full Deephaven system contains the most full-featured IDE. Running the full Deephaven system launches multiple Docker
187
-
containers, so it has the most overhead. This is a good option for interactively working with data.
188
-
189
-
See [./docker/full](./docker/full) for more details.
4) Launch the [Deephaven IDE](https://github.com/deephaven/deephaven-core/blob/main/README.md#run-deephaven-ide) by navigating to [http://localhost:10000/ide/](http://localhost:10000/ide/) in a browser.
207
-
208
-
209
-
### (Option 2) Launch pip-installed Deephaven with Docker -- interactive
177
+
### (Option 1) Launch pip-installed Deephaven with Docker -- interactive
210
178
211
179
The pip-installed Deephaven uses a lightweight Deephaven installation that is installed using pip. In this case,
212
180
the pip-installed Deephaven system is installed in a Docker container.
@@ -215,23 +183,19 @@ the pip-installed Deephaven system is installed in a Docker container.
3) Launch the [Deephaven IDE](https://github.com/deephaven/deephaven-core/blob/main/README.md#run-deephaven-ide) by navigating to [http://localhost:10000/ide/](http://localhost:10000/ide/) in a browser.
195
+
4) Launch the [Deephaven IDE](https://github.com/deephaven/deephaven-core/blob/main/README.md#run-deephaven-ide) by navigating to [http://localhost:10000/ide/](http://localhost:10000/ide/) in a browser.
232
196
233
197
234
-
### (Option 3) Launch pip-installed Deephaven with Docker -- run a script
198
+
### (Option 2) Launch pip-installed Deephaven with Docker -- run a script
235
199
236
200
The pip-installed Deephaven uses a lightweight Deephaven installation that is installed using pip. In this case,
237
201
the pip-installed Deephaven system is installed in a Docker container.
@@ -244,23 +208,19 @@ This is a good option for production scenarios where scripts need to be run and
244
208
# Set jvm_args to the desired JVM memory for Deephaven
3) Launch the [Deephaven IDE](https://github.com/deephaven/deephaven-core/blob/main/README.md#run-deephaven-ide) by navigating to [http://localhost:10000/ide/](http://localhost:10000/ide/) in a browser.
259
-
220
+
4) Launch the [Deephaven IDE](https://github.com/deephaven/deephaven-core/blob/main/README.md#run-deephaven-ide) by navigating to [http://localhost:10000/ide/](http://localhost:10000/ide/) in a browser.
260
221
261
-
### (Option 4) Launch pip-installed Deephaven with a local installation (No Docker) -- interactive
262
222
263
-
>**_NOTE:_** Deephaven pip install is not yet supported on all architectures. This launch should work on Linux (AMD64 and ARM64), Mac (M1 and Intel), and Windows WSL. It is not yet supported on Windows without WSL. For Windows, use WSL.
223
+
### (Option 3) Launch pip-installed Deephaven with a local installation (No Docker) -- interactive
264
224
265
225
The pip-installed Deephaven uses a lightweight Deephaven installation that is installed using pip. In this case,
266
226
the pip-installed Deephaven system is installed directly on your local system, without Docker.
@@ -285,14 +245,13 @@ new feature and has not been well tested. To do this:
285
245
4) Launch the system:
286
246
```bash
287
247
# Set jvm_args to the desired JVM memory for Deephaven
5) Launch the [Deephaven IDE](https://github.com/deephaven/deephaven-core/blob/main/README.md#run-deephaven-ide) by navigating to [http://localhost:10000/ide/](http://localhost:10000/ide/) in a browser.
291
252
6) Use `host="localhost"`forthe hostnamein the examples (Windows WSL uses `host="host.docker.internal"`, since WSL is built on Docker.)
292
253
293
-
### (Option 5) Launch pip-installed Deephaven with a local installation (No Docker) -- run a script
294
-
295
-
>**_NOTE:_** Deephaven pip install is not yet supported on all architectures. This launch should work on Linux (AMD64 and ARM64), Mac (M1 and Intel), and Windows WSL. It is not yet supported on Windows without WSL. For Windows, use WSL.
254
+
### (Option 4) Launch pip-installed Deephaven with a local installation (No Docker) -- run a script
296
255
297
256
The pip-installed Deephaven uses a lightweight Deephaven installation that is installed using pip. In this case,
298
257
the pip-installed Deephaven system is installed directly on your local system, without Docker.
@@ -317,7 +276,8 @@ new feature and has not been well tested. To do this:
317
276
```
318
277
4) Launch the system and execute a custom script:
319
278
```bash
320
-
# your_script.py must begin with: "from deephaven_server import Server; _server = Server(port=10000, jvm_args=['-Xmx4g']); _server.start()"
279
+
# your_script.py must begin with: "import os; from deephaven_server import Server; _server = Server(port=10000, jvm_args=['-Xmx4g','-Dstorage.path=' + os.path.expanduser('~/.deephaven')]); _server.start()"
280
+
# Deephaven IDE configuration and notebooks are stored to ~/.deephaven
321
281
# Set jvm_args to the desired JVM memory for Deephaven
Copy file name to clipboardExpand all lines: docker/dev/README.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ This directory contains the ingredients to build Docker images from the current,
4
4
5
5
This is useful when doing local development or when official images are not available for your platform.
6
6
7
+
In general, you will want to use the officially released images at [https://github.com/deephaven-examples/deephaven-ib/pkgs/container/deephaven-ib](https://github.com/deephaven-examples/deephaven-ib/pkgs/container/deephaven-ib).
8
+
7
9
## Build Image
8
10
9
11
```bash
@@ -12,8 +14,14 @@ This is useful when doing local development or when official images are not avai
12
14
13
15
## Run image in interactive mode
14
16
17
+
```bash
18
+
docker compose up
19
+
```
20
+
21
+
or
22
+
15
23
```bash
16
24
# Set jvm_args to the desired JVM memory for Deephaven
0 commit comments