Read on Twitter
One of the things I have to do often at Metabase is reproduce a problem in different versions. With Docker, it's easy to spin up different versions but configuring them has always been laborious.
Thanks to finally installing the @1Password CLI tool this just got a little easier!
Thanks to finally installing the @1Password CLI tool this just got a little easier!
I have one script that configures Metabase - it uses a default set of parameters, but importantly I can tweak the host/port.
So I spin up two different docker images on different ports and run the script twice, just changing the port between runs.
So I spin up two different docker images on different ports and run the script twice, just changing the port between runs.
Then I have a second script that can add a database. Now...I had never really finished this script because I didn't have a good way of not littering my database passwords all over my terminal history.
But finally, today, I installed the @1Password CLI!
But finally, today, I installed the @1Password CLI!
So now, I can just do:
DB_PASSWORD=$(op get item test-database --fields password) MB_PORT=3000 add_database.sh
for each instance and bada bing, bada boom I'm done!
DB_PASSWORD=$(op get item test-database --fields password) MB_PORT=3000 add_database.sh
for each instance and bada bing, bada boom I'm done!
This thread brought to you by a lazy sysadmin.
(Also, I have a nifty Docker image that can execute these scripts in a containerized environment as well, but I haven't gotten the add_database one wired up yet.)
