mirror of
https://github.com/apache/superset.git
synced 2026-04-20 00:24:38 +00:00
fix: support docker/.env-local for docker-compose (#28039)
This commit is contained in:
committed by
GitHub
parent
8538796128
commit
0c12369084
@@ -112,6 +112,7 @@ with docker compose will store that data in a PostgreSQL database contained in a
|
||||
[volume](https://docs.docker.com/storage/volumes/), which is not backed up.
|
||||
|
||||
Again **DO NOT USE THIS FOR PRODUCTION**
|
||||
|
||||
:::
|
||||
|
||||
You should see a wall of logging output from the containers being launched on your machine. Once
|
||||
@@ -137,6 +138,13 @@ are helpful for learning and testing out Superset but unnecessary for experience
|
||||
production deployments. The loading process can sometimes take a few minutes and a good amount of
|
||||
CPU, so you may want to disable it on a resource-constrained device.
|
||||
|
||||
For more advanced or dynamic configurations that are typically managed in a `superset_config.py` file
|
||||
located in your `PYTHONPATH`, note that it can be done by providing a
|
||||
`docker/pythonpath_dev/superset_config_docker.py` that will be ignored by git
|
||||
(preventing you to commit/push your local configuration back to the repository).
|
||||
The mechanics of this are in `docker/pythonpath_dev/superset_config.py` where you can see
|
||||
that the logic runs a `from superset_config_docker import *`
|
||||
|
||||
|
||||
:::note
|
||||
Users often want to connect to other databases from Superset. Currently, the easiest way to
|
||||
|
||||
Reference in New Issue
Block a user