From c43d203a6b568963c86171523166cc35e8f29d57 Mon Sep 17 00:00:00 2001 From: Austin Macdonald Date: Wed, 7 Aug 2024 20:09:13 -0500 Subject: [PATCH] Feedback from @viniciusdc --- docs/docs/how-tos/nebari-local.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/docs/docs/how-tos/nebari-local.md b/docs/docs/how-tos/nebari-local.md index 110e3fd5..59bf948e 100644 --- a/docs/docs/how-tos/nebari-local.md +++ b/docs/docs/how-tos/nebari-local.md @@ -73,6 +73,11 @@ The following steps assume you have: 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) ::: +:::note +If you are deploying locally, DNS is not necessary except for dask dashboard and the notebook +scheduler extension. Therefore for test deployments it is recommended leave out the `--domain` option. +::: + Once `nebari init` is executed, you should then be able to see the following output: ```bash @@ -124,6 +129,8 @@ If you are a Linux user, you can use the `sudo` command to gain root privileges sudo echo "172.18.1.100 " | sudo tee -a /etc/hosts ``` +See the [domain-registry documentation](https://www.nebari.dev/docs/how-tos/domain-registry#what-is-a-dns) for details. + ::: ### Exposing container network (for MacOS) @@ -159,14 +166,6 @@ security: tag: sha-b4a2d1e ``` -### Disable DNS for local deployment - -If you are deploying locally, DNS is not necessary except for dask dashboard and the notebook -scheduler extension. Therefore it is recommended to simply delete the `domain` line from the -`nebari-config.yaml`. - -If you prefer to setup DNS, see the [domain-registry documentation](https://www.nebari.dev/docs/how-tos/domain-registry#what-is-a-dns). - ## Deploying Nebari With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time with: