Vucko95 opened a new issue, #30187:
URL: https://github.com/apache/superset/issues/30187

   ### Bug description
   
   Why once user defines `SUPERSET_DATABASE_URI`, connection between Superset 
and DB is not automatically set.
   
   This is ENV variable that I define:
   
`SUPERSET_DATABASE_URI=postgresql://superset:superset_password@postgres:5432/superset_db`
   and when I run my Docker-compose , Superset and Posgresql are up but,
   When I log to Superset UI , Posgresql connection is not automatically set, 
but I have provided ENV variable.
   When I try to test connection manually it is working.(Check the picture, My 
main goal is skip this manual step)
   
   ### How to reproduce the bug
   
   `version: '3'
   services:
   
     superset5:
         build:
           context: ./superset
           dockerfile: dockerfile
         container_name: superset5
         environment:
           - ADMIN_USERNAME=admin
           - ADMIN_EMAIL=ad...@superset.com
           - ADMIN_PASSWORD=admin
           - SUPERSET_SECRET_KEY=super_ssecret 
           - 
SUPERSET_DATABASE_URI=postgresql://superset:superset_password@postgres:5432/superset_db
         ports:
           - '8088:8088'
         depends_on:
           - postgres
   
     postgres:
       image: postgres:14
       container_name: postgres
       environment:
         POSTGRES_USER: superset
         POSTGRES_PASSWORD: superset_password
         POSTGRES_DB: superset_db
       ports:
         - '5432:5432'
       volumes:
         - postgres_data:/var/lib/postgresql/data
         - ./init.sql:/docker-entrypoint-initdb.d/init.sql`
   
   ### Screenshots/recordings
   
   
![image](https://github.com/user-attachments/assets/4fb488e9-67f0-4a1e-af69-1bc885598d36)
   
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to