You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should open the database (or ask the user to start the project).
Actual Behavior
When I tested ddev dbeaver with a stopped project, it started the project and tried to open the database with 3306 port (which is not the correct host port), and on the second run the db was opened with the actual working port.
Steps To Reproduce
ddev stop
ddev dbeaver (or any other db command)
see the database connection with the wrong port
Anything else?
I assume that this is because the DDEV env variables in the dbeaver script (and any other script for opening a database) are not updated after ddev start, so it only works when the project is started.
Is it possible to update env in Bash after ddev start? Or maybe we need to change the logic for db commands from:
if [ "${DDEV_PROJECT_STATUS}"!="running" ];thenecho"Project ${DDEV_PROJECT} is not running, starting it"
ddev start
fi
to
if [ "${DDEV_PROJECT_STATUS}"!="running" ];thenecho>&2"Project ${DDEV_PROJECT} is not running, please start it"exit 1
fi
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Output of
ddev debug test
Expand `ddev debug test` diagnostic information
Expected Behavior
It should open the database (or ask the user to start the project).
Actual Behavior
When I tested
ddev dbeaver
with a stopped project, it started the project and tried to open the database with3306
port (which is not the correct host port), and on the second run the db was opened with the actual working port.Steps To Reproduce
ddev stop
ddev dbeaver
(or any other db command)Anything else?
I assume that this is because the DDEV env variables in the
dbeaver
script (and any other script for opening a database) are not updated afterddev start
, so it only works when the project is started.Is it possible to update env in Bash after
ddev start
? Or maybe we need to change the logic for db commands from:to
The text was updated successfully, but these errors were encountered: