<https://meltano.slack.com/archives/CFG3C3C66/p159...
# announcements
k
https://meltano.slack.com/archives/CFG3C3C66/p1595256121250900?thread_ts=1595254380.244100&amp;cid=CFG3C3C66 @douwe_maan Yeah, the default.
Copy code
meltano config meltano list | grep uri
database_uri [env: MELTANO_DATABASE_URI] current value: 'sqlite:////Users/bla/.meltano/meltano.db' (from default: 'sqlite:///$MELTANO_PROJECT_ROOT/.meltano/meltano.db')
Honestly, no biggies, did
meltano config meltano set
and it works. Was hoping to see magic of export ing to env var and seeing it gets updated for all meltano command hahahaha
d
I can't explain what you're seeing unfortunately, it works just as expected here:
Copy code
$ export MELTANO_DATABASE_URI=<postgresql://meltano:meltano@localhost:5432/system-database>
$ meltano config meltano list
database_uri [env: MELTANO_DATABASE_URI] (default: 'sqlite:///$MELTANO_PROJECT_ROOT/.meltano/meltano.db') current value: '<postgresql://meltano:meltano@localhost:5432/system-database>' (from the environment)
I'm glad it's not a blocker, but it's very confusing!
m
ok, I did that and it's not working for me, checking again with new project.
Do I need to run something after I configure the database uri?
Like init the database schema etc ..?
d
m
ok, so nothing to do after the configuration
d
Correct
Would you be willing to jump on a quick Zoom call so I can help you debug this a little more while seeing the relevant screens?
m
thank you, checking
it looks like the database issue was solved
d
Oh cool! 😄 What changed?
m
new project