Skip to content

Commit c43d203

Browse files
committed
Feedback from @viniciusdc
1 parent aaff895 commit c43d203

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

docs/docs/how-tos/nebari-local.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,11 @@ The following steps assume you have:
7373
Note You will be prompted to enter values for some of the choices above if they are absent from the command line arguments (for example, project name and domain)
7474
:::
7575

76+
:::note
77+
If you are deploying locally, DNS is not necessary except for dask dashboard and the notebook
78+
scheduler extension. Therefore for test deployments it is recommended leave out the `--domain` option.
79+
:::
80+
7681
Once `nebari init` is executed, you should then be able to see the following output:
7782

7883
```bash
@@ -124,6 +129,8 @@ If you are a Linux user, you can use the `sudo` command to gain root privileges
124129
sudo echo "172.18.1.100 <domain>" | sudo tee -a /etc/hosts
125130
```
126131

132+
See the [domain-registry documentation](https://www.nebari.dev/docs/how-tos/domain-registry#what-is-a-dns) for details.
133+
127134
:::
128135

129136
### Exposing container network (for MacOS)
@@ -159,14 +166,6 @@ security:
159166
tag: sha-b4a2d1e
160167
```
161168
162-
### Disable DNS for local deployment
163-
164-
If you are deploying locally, DNS is not necessary except for dask dashboard and the notebook
165-
scheduler extension. Therefore it is recommended to simply delete the `domain` line from the
166-
`nebari-config.yaml`.
167-
168-
If you prefer to setup DNS, see the [domain-registry documentation](https://www.nebari.dev/docs/how-tos/domain-registry#what-is-a-dns).
169-
170169
## Deploying Nebari
171170
172171
With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time with:

0 commit comments

Comments
 (0)