Skip to content

Commit 280dfcf

Browse files
authored
Merge pull request #27 from metabase/add-presto-for-mac-instructions
2 parents 0a30f7c + 46c400a commit 280dfcf

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

README.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Your startup command could then look as following:
4848

4949
If you are running the app db in docker container from images in this repo you need to pass in also the correct credentials, eg. `MB_JETTY_PORT=10001 MB_DIR=path/to/your/mb/repo bb --config /path/to/this/repo/bb.edn metabuild -d postgres -u metabase -p Password1234 -e dev:ee:ee-dev:drivers:drivers-dev:vsc`
5050

51-
#### Passing
51+
#### Passing
5252

5353
### Database Scripts
5454

@@ -80,6 +80,23 @@ The work around is using colima:
8080
2. Start it with `colima start --arch x86_64 --memory 4`
8181
3. Start the database with scripts like normal
8282

83+
#### Presto on Macbook with ARM chips
84+
85+
Rather than use Docker, you can run Presto with Postgres with the following steps:
86+
- Follow [these
87+
steps](https://prestodb.io/docs/current/installation/deploy-brew.html#deploy-presto-on-an-apple-silicon-mac-using-homebrew)
88+
to install presto using homebrew
89+
- Add a properties file for postgresql in `/usr/local/Cellar/prestodb/<version>/libexec/etc/catalog`, called `postgresql.properties` with the following contents:
90+
```
91+
connector.name=postgresql
92+
connection-url=jdbc:postgresql://localhost:5432/test-data
93+
connection-user=<mb-postgresql-test-user>
94+
connection-password=<mb-postgresql-test-password>
95+
```
96+
- Start the presto server with `/usr/local/opt/prestodb/bin/presto-server run`
97+
98+
Alternatively, Luis has created a [Link](https://github.com/paoliniluis/metabase-presto-and-trino) for testing Presto and Trino with Docker that might work too.
99+
83100
# Automated setup
84101

85102
In stacks->setup-container you'll find a Compose file that has a Metabase container along with a setup container. The setup container waits till the Metabase container is ready (status:ok in the health endpoint) and then sets up a user (a@b as the user/ metabot1 as the password). You can tweak the script as much as you want.

0 commit comments

Comments
 (0)