metabase / metabase-heroku Goto Github PK

License: GNU Affero General Public License v3.0

Shell 100.00%

metabase-heroku's Introduction

Metabase

Metabase is the easy, open-source way for everyone in your company to ask questions and learn from data.

Get started

The easiest way to get started with Metabase is to sign up for a free trial of Metabase Cloud. You get support, backups, upgrades, an SMTP server, SSL certificate, SoC2 Type 2 security auditing, and more (plus your money goes toward improving Metabase). Check out our quick overview of cloud vs self-hosting. If you need to, you can always switch to self-hosting Metabase at any time (or vice versa).

Features

Set up in five minutes (we're not kidding).
Let anyone on your team ask questions without knowing SQL.
Use the SQL editor for more complex queries.
Build handsome, interactive dashboards with filters, auto-refresh, fullscreen, and custom click behavior.
Create models that clean up, annotate, and/or combine raw tables.
Define canonical segments and metrics for your team to use.
Send data to Slack or email on a schedule with dashboard subscriptions.
Set up alerts to have Metabase notify you when your data changes.
Embed charts and dashboards in your app, or even your entire Metabase.

Take a tour of Metabase.

Supported databases

Installation

Metabase can be run just about anywhere. Check out our Installation Guides.

Contributing

Quick Setup: Dev environment

In order to spin up a development environment, you need to start the front end and the backend as follows:

Frontend quick setup

The following command will install the Javascript dependencies:

$ yarn install

To build and run without watching changes:

$ yarn build

To build and run with hot-reload:

$ yarn build-hot

Backend quick setup

In order to run the backend, you'll need to build the drivers first, and then start the backend:

$ ./bin/build-drivers.sh
$ clojure -M:run

For a more detailed setup of a dev environment for Metabase, check out our Developers Guide.

Internationalization

We want Metabase to be available in as many languages as possible. See which translations are available and help contribute to internationalization using our project over at POEditor. You can also check out our policies on translations.

Extending Metabase

Hit our Query API from Javascript to integrate analytics. Metabase enables your application to:

Build moderation interfaces.
Export subsets of your users to third party marketing automation software.
Provide a custom customer lookup application for the people in your company.

Check out our guide, Working with the Metabase API.

Security Disclosure

See SECURITY.md for details.

License

This repository contains the source code for both the Open Source edition of Metabase, released under the AGPL, as well as the commercial editions of Metabase, which are released under the Metabase Commercial Software License.

See LICENSE.txt for details.

Metabase Experts

If you’d like more technical resources to set up your data stack with Metabase, connect with a Metabase Expert.

metabase-heroku's People

Contributors

Stargazers

Watchers

Forkers

nfm backus heliostatic chowdhary987 jonymusky cnxtech abdala9512 iamkavinash isabella232

metabase-heroku's Issues

Question about updating on Heroku

It looks like www.github.com/metabase/metabase-deploy is not updated to 0.28.1
Is there some way to perhaps use this repo (metabase-heroku) for that. Or is there another workaround?

Please also let me know if I should ask this somewhere else.

Thanks, Edwin

Buildpack error attempting to upgrade to 0.25.

I'm attempting to upgrade my Heroku deployment to 0.25 following the instructions found here: http://www.metabase.com/docs/latest/operations-guide/running-metabase-on-heroku.html but when I attempt to push master to heroku, it is being rejected by the buildpack:

Here's what I'm seeing:

$ git clone https://github.com/metabase/metabase-deploy.git
Cloning into 'metabase-deploy'...
remote: Counting objects: 411, done.
remote: Total 411 (delta 0), reused 0 (delta 0), pack-reused 411
Receiving objects: 100% (411/411), 1.06 GiB | 4.42 MiB/s, done.
Resolving deltas: 100% (182/182), done.
Checking connectivity... done.

$ cd metabase-deploy
$ git remote add heroku https://git.heroku.com/[my-metabase-app].git
$ heroku buildpacks:add https://github.com/metabase/metabase-heroku
Buildpack added. Next release on [my-metabase-app] will use:
  1. https://github.com/heroku/heroku-buildpack-jvm-common.git
  2. https://github.com/metabase/metabase-heroku
Run git push heroku master to create a new release using these buildpacks.
$ git push -f heroku master
Counting objects: 31, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (31/31), 4.19 KiB | 0 bytes/s, done.
Total 31 (delta 17), reused 30 (delta 16)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> JVM Common app detected
remote: -----> Installing OpenJDK 1.8... done
remote: -----> Failed to detect app matching https://github.com/metabase/metabase-heroku buildpack
remote:        More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:
remote: !	Push rejected to /[my-metabase-app].
remote:
To https://git.heroku.com//[my-metabase-app].git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com//[my-metabase-app].git'

Need to reset heroku repo to deploy new version

Hi,

Metabase is running on Heroku. When we upgrade, it's not enough to just push this code to the Heroku repo again:

->metabase-deploy git:(master) git remote -v
heroku https://git.heroku.com/woo-kpi-prod.git (fetch)
heroku https://git.heroku.com/woo-kpi-prod.git (push)
origin https://github.com/metabase/metabase-deploy.git (fetch)
origin https://github.com/metabase/metabase-deploy.git (push)
->metabase-deploy git:(master) git pull origin
Already up-to-date.
->metabase-deploy git:(master) git push -f heroku master
Everything up-to-date

Heroku seems to believe that nothing has changed, so if refuses to re-deploy.

Currently, the workaround is to reset the repo using: https://github.com/heroku/heroku-repo, then pushing to the Heroky repo again.

Perhaps there is a better way of doing this? If it's not possible to fix this problem from Metabase side, I think it would be a good idea to mention it in the docs.

Use this instead of metabase-deploy?

Just noticed this repo. Which seems to be a more up-to-date version on metabase-deploy. Should we use this repo going forward when upgrading heroku builds?