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
get websocketfs to mount even "on my laptop", i.e., for some reason allowOther isn't supported, and it's better to work without root being allowed (which I think we don't need), then to mysteriously fail
Copy file name to clipboardExpand all lines: src/compute/compute/dev/README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,14 @@ The scripts here are helpful for developing the compute\-server manager, which i
3
3
1. Create the directory /tmp/user and make sure you can read it. Maybe even mount it from the target project.
4
4
5
5
2. The conf/ directory here has the same files as on /cocalc/conf in an actual compute\-server, except:
6
-
- replace api_server by something like `http://localhost:5000/6659c2e3-ff5e-4bb4-9a43-8830aa951282/port/5000`, where the port is what you're using for your dev server and the project id is of your dev server. The point is that we're going to connect directly without going through some external server.
6
+
- replace api_server by something like `http://127.0.0.1:5000/6659c2e3-ff5e-4bb4-9a43-8830aa951282/port/5000`, where the port is what you're using for your dev server and the project id is of your dev server. The point is that we're going to connect directly without going through some external server.
7
7
- api_key: the one from an actual server will get deleted when you turn that server off, so make a different project level api key.
8
8
9
-
Type `tar xvf conf.tar` to get a template for the conf directory. You will need to change the contents
10
-
of all the files you get, as mentioned above!
9
+
Type `tar xvf conf.tar` to get a template for the conf directory.
10
+
You will need to change the contents of all the files you get, as
11
+
mentioned above! Also, regarding the api_server, be especially careful
12
+
about ipv4 versus ipv6, e.g., use 127.0.0.1 instead of localhost to
13
+
nail down the protocol.
11
14
12
15
This is potentially confusing, and when developing this it was 10x worse... Maybe you'll be confused for 2 hours instead of 2 days.
0 commit comments