Skip to content

Document metabase optional configuration (email, ...) #1136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 18, 2025
Merged

Document metabase optional configuration (email, ...) #1136

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions services/metabase/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,3 +6,20 @@ Before deploying metabase first time, make sure that postgres is configured:
* you can get one via adminer or by directly connecting to container and executing `psql -U <user> -d <db>`

This can be automated via https://github.com/ITISFoundation/osparc-ops-environments/issues/827

## Extra Configuration (optional)

Setting up email (manual):
* go to admin settings
* go to email
* configure email using SMTP_HOST, SMTP_PASSWORD, SMTP_PORT, SMTP_PROTOCOL, SMTP_USERNAME env from config
- Note: `FROM NAME` shall potentially clearly indicate deployment (if we use metabase in multiple deployments this helps to avoid confusion)
- Note: `FROM ADDRESS` use support email (we may consider adding a separate user and mail for metabase later)
- Note: `REPLY-TO ADDRESS` must NOT be support email. Feel free to choose some of backenders / devops email

Configuring localization (manual):
* go to admin settings
* go to localization
* configure first day of the week to be `Monday`

Note: later these manual steps can be automated via Metabase API calls
Loading