Skip to content

Commit 47d3448

Browse files
committed
sandboxing page updates
1 parent dae46fc commit 47d3448

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

docs/src/content/docs/guides/sandboxing.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ We'll be using Oracle VirtualBox for this example.
2626
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.
2727
You can find guides online if you don't know how.
2828

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.
3030

3131
1. Open your VM's settings and navigate to the Network section.
3232

@@ -44,17 +44,17 @@ If you're comfortable with not having internet access in the VM, you can stay in
4444

4545
3. After selecting that, make sure you note down the name of the adapter.
4646

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).
4848

4949
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.
5050

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:
5252

5353
7. Now, connect to your virtual machine and install NeuroPilot.
5454

5555
8. Open your settings, and go down to the [`NeuroPilot > Websocket Url`](/neuropilot/reference/settings#websocket-url).
5656

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)`.
5858

5959
10. Now, [attempt to reconnect](/neuropilot/reference/commands#reconnect). This should now connect to your Neuro API server as expected.
6060

@@ -65,7 +65,7 @@ As of v2.2.0, NeuroPilot now has a separate Web build. It acts partially the sam
6565
This includes:
6666

6767
- 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.)
6969
- Copilot Chat window & inline completions (dependency extension can't be ran in the web environment)
7070

7171
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

Comments
 (0)