This is an automated email from the ASF dual-hosted git repository. tai pushed a commit to branch nytai-patch-2 in repository https://gitbox.apache.org/repos/asf/superset.git
commit e55cb733ba89d2833a63f1498225bdacf856c520 Author: ʈᵃᵢ <[email protected]> AuthorDate: Mon Sep 18 17:36:49 2023 -0400 Update docker-compose docs --- .../installing-superset-using-docker-compose.mdx | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/docs/installation/installing-superset-using-docker-compose.mdx b/docs/docs/installation/installing-superset-using-docker-compose.mdx index d0451fb19a..54d43b0df3 100644 --- a/docs/docs/installation/installing-superset-using-docker-compose.mdx +++ b/docs/docs/installation/installing-superset-using-docker-compose.mdx @@ -62,6 +62,9 @@ When working on master branch, run the following commands to run `development` m ```bash docker compose up ``` +:::tip +When running in development mode the `superset-node` container needs to finish building assets in order for the UI to render properly. If you would just like to try out Superset without making any code changes follow the steps documented for `production` or a specific version bellow. +::: When working on master branch, run the following commands to run `production` mode using `docker compose`: @@ -75,9 +78,9 @@ the branch/tag, and then starting `docker-compose` with the `TAG` variable. For example, to run the 2.1.0 version, run the following commands: ```bash -git checkout 2.1.0 -TAG=2.1.0 docker-compose -f docker-compose-non-dev.yml pull -TAG=2.1.0 docker-compose -f docker-compose-non-dev.yml up +git checkout 3.0.0 +TAG=3.0.0 docker-compose -f docker-compose-non-dev.yml pull +TAG=0.0.0 docker-compose -f docker-compose-non-dev.yml up ``` :::tip @@ -94,10 +97,6 @@ You should see a wall of logging output from the containers being launched on yo this output slows, you should have a running instance of Superset on your local machine! To avoid the wall of text on future runs, add the `-d` option to the end of the `docker-compose up` command. -**Note:** This will bring up superset in a non-dev mode, changes to the codebase will not be reflected. -If you would like to run superset in dev mode to test local changes, simply replace the previous command with: `docker-compose up`, -and wait for the `superset_node` container to finish building the assets. - #### Configuring Docker Compose The following is for users who want to configure how Superset runs in Docker Compose; otherwise, you can skip to the next section.
