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
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,6 +98,24 @@ npm install -g ijavascript
98
98
ijsinstall
99
99
```
100
100
101
+
# Using remote runtime
102
+
103
+
In the runtime section in the sidebar, you can add a new runtime. For the runtime, you need to specify the two addresses: the websocket address for sending code to server, and the MQ address for receiving output. If MQ address is empty, the websocket will be used.
104
+
105
+
The default runtime is the local runtime, which is `localhost:14321`
106
+
107
+
To start the server, on the server machine, you need to setup the kernels. Then, you need to clone this repo, go into the cpkernel folder, and do:
108
+
109
+
1.`docker-compose up -d`. This will setup a rabbitmq server. The MQ address is `:15674`
110
+
2.`npm run kernel-server`. This will run the server. The websocket address is `:14321`
111
+
112
+
So to use this server, enter:
113
+
114
+
-`<your-server-ip>:14321` for the socket address
115
+
-`<your-server-ip>:15674` for the MQ address
116
+
117
+
We can spawn a docker container on the server for the kernels. However, it will be tricky to access files and install packages. One has to install packages for every restart of the kernel, and one has to mount a volume to exchange files between the server and the container. Thus we think it is a better experience to use the bare-metal server.
0 commit comments