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: src/edgedb-cli/NOTES.md
+15-3Lines changed: 15 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,18 @@
1
-
## Note to Users
1
+
## Usage
2
2
3
-
This feature mounts the edgedb config and data folder to the host machine for persistence. To do so, it makes some assumptions about `edgedb info`:
3
+
**The EdgeDB instance should not be in the same container as the CLI.** My experience doing so makes the `edgedb ui` command start failing once you restart the container. I recommend the following options:
4
+
5
+
1. Use a docker-compose template with two services: one for the CLI and one for the EdgeDB instance.
6
+
7
+
You can either use the [javascript-node-edgedb](https://github.com/joshuanianji/devcontainer-templates/blob/main/src/javascript-node-edgedb) or the [rust-edgedb](https://github.com/joshuanianji/devcontainer-templates/blob/main/src/rust-edgedb) templates, or use them as references to make your own.
8
+
9
+
Once inside the devcontainer, you can run `edgedb instance link` to connect the CLI to the instance. Check the templates above for more details.
10
+
11
+
2. Connect to a cloud instance [with `edgedb cloud`](https://docs.edgedb.com/cloud/cli).
12
+
13
+
## Notes on Volume Mounts
14
+
15
+
This feature mounts the edgedb config and data folder for persistence. To do so, it makes some assumptions about `edgedb info`:
4
16
5
17
```bash
6
18
$ edgedb info
@@ -15,7 +27,7 @@ EdgeDB uses the following local paths:
0 commit comments