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
i'm attempting to write my first driver and at the step of wanting to bring up a development server with it loaded and test connecting to a database, but stuck. the example here looks great but must be out of date. same with the one in https://github.com/metabase/sudoku-driver#hacking-on-the-driver-locally the "run" alias doesn't seem to exist. https://www.metabase.com/docs/latest/developers-guide/drivers/start doesn't seem to have info on this either what's the latest and greatest for getting my new driver to connect to a database without just dropping it into a production metabase server and hoping the logs are good enough to debug?
The text was updated successfully, but these errors were encountered:
actually if i cd into my metabase directory then i can do "clojure -M:user/my-driver:run" it does bring up http://localhost:3000 but maybe should have just run from the metabase jar instead of attempting to build it from source since then you have to do the frontend build also and i spent forever on some nodejs stuff.
for anyone else stuck: on the current node LTS (v18.12.1) and os x 12.5.1 I had to edit metabase/package.json as follows:
i'm attempting to write my first driver and at the step of wanting to bring up a development server with it loaded and test connecting to a database, but stuck. the example here looks great but must be out of date. same with the one in https://github.com/metabase/sudoku-driver#hacking-on-the-driver-locally the "run" alias doesn't seem to exist. https://www.metabase.com/docs/latest/developers-guide/drivers/start doesn't seem to have info on this either what's the latest and greatest for getting my new driver to connect to a database without just dropping it into a production metabase server and hoping the logs are good enough to debug?
The text was updated successfully, but these errors were encountered: