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: docs/src/content/docs/guides/sandboxing.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ We'll be using Oracle VirtualBox for this example.
26
26
We'll assume that you have set up a virtual machine and figured out a way to connect to it; whether that be SSH or Tunnels.
27
27
You can find guides online if you don't know how.
28
28
29
-
In order to not have to expose the Neuro API server to the internet, we'll use a **Host-Only Adapter** network, which essentially creates a local system.
29
+
In order to not have to expose the Neuro API server to the internet, we'll use a **Host-Only Adapter** network, which essentially creates a local network to two-way interact with a VM.
30
30
31
31
1. Open your VM's settings and navigate to the Network section.
32
32
@@ -44,17 +44,17 @@ If you're comfortable with not having internet access in the VM, you can stay in
44
44
45
45
3. After selecting that, make sure you note down the name of the adapter.
46
46
47
-
4. On your host machine, open your console and run `ipconfig /all` (Windows) or `ip a` (macOS/Linux). Then, take note of what your assigned IP is for the adapter that has the description containing the name you noted down earlier.
47
+
4. On your host machine, open your console and run `ipconfig /all` (Windows) or `ip a` (macOS/Linux).
48
48
49
49
5. Take note of the IP listed there. If you're on Windows and ran `ipconfig /all`, note down the IPv4 address that has `(Preferred)` next to it.
50
50
51
-
6. Start your Neuro API server on that address. If you're using one of the testing tools on the official API repo's README, you should be able to pass a CLI flag to spawn it on a certain host.
51
+
6. Start your Neuro API server on that address. If you're using one of the testing tools on the official API repo's README, you should be able to pass a CLI flag to spawn it on a certain host. If you're Vedal and you're using Neuro, uhhh good luck :thumbsup:
52
52
53
53
7. Now, connect to your virtual machine and install NeuroPilot.
54
54
55
55
8. Open your settings, and go down to the [`NeuroPilot > Websocket Url`](/neuropilot/reference/settings#websocket-url).
56
56
57
-
9. Add your IP address and host that you spawned your Neuro API server on, in the scheme of `ws://(host):(port)`.
57
+
9. Add the host IP address and port that you spawned your Neuro API server on, in the scheme of `ws://(host):(port)`.
58
58
59
59
10. Now, [attempt to reconnect](/neuropilot/reference/commands#reconnect). This should now connect to your Neuro API server as expected.
60
60
@@ -65,7 +65,7 @@ As of v2.2.0, NeuroPilot now has a separate Web build. It acts partially the sam
65
65
This includes:
66
66
67
67
- Terminals & tasks
68
-
- Git access
68
+
- Git access (it *is* activated in certain situations, but debugging this in a test environment is impossible and also it functions slightly differently, therefore, for stability, it has been disabled.)
69
69
- Copilot Chat window & inline completions (dependency extension can't be ran in the web environment)
70
70
71
71
To use the web version, go to [vscode.dev](https://vscode.dev) (or any web build of VS Code, such as `github.dev`), and install NeuroPilot.
0 commit comments