You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by ta...@apache.org on 2023/09/18 21:49:09 UTC
[superset] branch nytai-patch-2 updated (e55cb733ba -> d24f23e683)
This is an automated email from the ASF dual-hosted git repository.
tai pushed a change to branch nytai-patch-2
in repository https://gitbox.apache.org/repos/asf/superset.git
omit e55cb733ba Update docker-compose docs
new d24f23e683 Update docker-compose docs
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (e55cb733ba)
\
N -- N -- N refs/heads/nytai-patch-2 (d24f23e683)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/docs/installation/installing-superset-using-docker-compose.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[superset] 01/01: Update docker-compose docs
Posted by ta...@apache.org.
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 d24f23e6833274a94bdc2b2b7414a771497d0bd2
Author: ʈᵃᵢ <td...@gmail.com>
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..dfa0b6c677 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.