-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Condense slack messages into one * Updating Data Monitors to be a dropdown * Update documentation images * Fix execution timestamp update error * Fix incorrect zscore calculations * Decrease dockerfile size * Add GA tag to our documentation * Zscores bug fix * Add sampling for data points instead of backfill on timestamp * Add freshness metric check for timestamp columns * update readme copy and images * Show healthiness status on a metric * Fix metric id equality join * Add algolia search * Update postgresql class * Add to user setup process * Block usage on preferences set * Update docs colors * Add issues page and model * Add webhook integration support * add sqlalchemy-bigquery dependency * add bigquery logo & update image folder structure * add support for bigquery datasource in UI * add bigquery driver * update logo link & fix class overrides * fix timestamp cast for bq freshness monitor * add BigQuery to docs * fix redshift freshness monitor syntax * Fix missing monitors * remove timestamp filter on frontend * fix metric type detection for bigquery * fix bq config * update contributing docs * Revert "add BigQuery to docs" This reverts commit 9b426a5. * Add bigquery Co-authored-by: Kevin Unkrich <[email protected]>
- Loading branch information
Showing
71 changed files
with
1,565 additions
and
291 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,15 +23,7 @@ Bug reports help make monosi better for everyone. To create a bug report, [raise | |
|
||
## Development Environment Setup | ||
|
||
To get the project setup locally and be ready for development: | ||
|
||
1. Fork the repository | ||
2. Clone the repository to your development machine & navigate into it | ||
3. Start a python virtual environment `python3 -m virtualenv .venv && source .venv/bin/activate` | ||
4. Run `make init` | ||
5. Install the current dev version by running `python3 -m setup.py install` | ||
|
||
You are now running the development version of monosi. If you have any questions, reach out on Slack | ||
Please follow the [instructions outlined in the Monosi docs](https://docs.monosi.dev/docs/contributing/local-development) to get set up with a local instance of the project for development. | ||
|
||
## First-time contributors | ||
|
||
|
@@ -51,6 +43,6 @@ If you want to speak to us before doing lots of work, just ping us in [Slack](ht | |
|
||
## Questions | ||
|
||
Come say hi to us on [Slack](https://monosi.dev/slack)! :wave: | ||
Come say hi to us on [Slack](https://monosi.dev/slack)! 👋 | ||
|
||
Or if you prefer, email us at [[email protected]](mailto:[email protected]) — we're always happy to chat! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,5 +4,39 @@ title: Local Development Setup | |
sidebar_label: Local Development | ||
--- | ||
|
||
Learn how to build Monosi from source using the following YouTube guide: | ||
https://www.youtube.com/watch?v=OsVKKo71Z70 | ||
The directions below outline the process for setting up Monosi for local development. To get started: | ||
|
||
1. Create a fork of the Monosi repository to your personal GitHub account | ||
2. Clone the fork URL that you have created to your local machine (`git clone <fork-url>`) | ||
|
||
Monosi can be installed either through docker or through a local dependency setup. | ||
## Running with Docker | ||
|
||
1. Ensure that you have installed docker and it is running on your machine | ||
2. In a terminal, navigate to the cloned repository | ||
3. Run `make compose-build` from the base of the directory to build a local instance of Monosi | ||
4. Run `make compose-run` from the base of the directory to run the local build | ||
5. Navigate to `http://localhost:3000` and you will see the Monosi UI | ||
|
||
For any changes you make to the code locally, you can test them by re-running steps 3 & 4. | ||
## Running without Docker | ||
|
||
1. Ensure that you have Python3, Node, and Yarn on your machine | ||
2. In a terminal, navigate to the cloned repository | ||
|
||
For the server: | ||
1. Create a Python virtualenv by running `virtualenv .venv` | ||
|
||
2. Activte the virtualenv by running `source .venv/bin/activate` | ||
3. Install the Monosi dependencies by running `python3 setup.py install` | ||
4. Navigate to the server directory `cd src/server` | ||
5. Run `flask run` | ||
6. You should see the server startup and become accessible at `http://localhost:5000` | ||
|
||
For the client: | ||
1. Navigate to the ui directory `cd src/ui` | ||
2. Run `yarn && yarn start` | ||
3. The React application should start on `localhost:3000` | ||
|
||
|
||
If there's any problems with the setup, please send us a message in the [Slack](https://monosi.dev/slack) or over [email](mailto:[email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,5 +3,51 @@ id: contributing-overview | |
title: Contributing Overview | ||
sidebar_label: Overview | ||
--- | ||
# Contributing to monosi | ||
|
||
We would love to have you contribute to Monosi. You can start by joining our [Slack community](https://monosi.dev/slack) to learn more about how to get involved. | ||
Thank you for considering contributing to monosi! There are many types of contributions you can make, including bug reports and fixes, writing tutorials, and larger feature requests or changes. | ||
|
||
Before you contribute, make sure to read these guidelines thoroughly, so that you can get your pull request reviewed and finalized as quickly as possible. | ||
|
||
- [Reporting Issues](#reporting-issues) | ||
- [Feature requests](#feature-requests) | ||
- [Development Environment Setup](#development-environment-setup) | ||
- [First-time contributors](#first-time-contributors) | ||
- [Creating a PR](#creating-a-pr) | ||
- [Questions](#questions) | ||
|
||
> **Note:** we're a young project and our contribution process is actively evolving. If you'd like to suggest or discuss changes to this document or the process in general, we're very open to suggestions and would appreciate if you reach out on [Slack](https://monosi.dev/slack) or at [[email protected]](mailto:[email protected])! To suggest additions to this document, feel free to raise an issue or make a PR with the changes. | ||
## Reporting Issues | ||
|
||
Bug reports help make monosi better for everyone. To create a bug report, [raise an issue](https://github.com/monosidev/monosi/issues/new?assignees=&labels=bug&template=bug_report.md&title=) using the "Bug Report" template. This template will provide you with a structure so we can best recreate the issue and promptly respond. Please search within our issues before raising a new one to make sure you're not raising a duplicate. | ||
|
||
## Feature requests | ||
|
||
[Raise an issue](https://github.com/monosidev/monosi/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=) using the "Feature Request" template and make sure it's tagged as an `enhancement`. We love every idea. Please give us as much context on the "why" as possible. | ||
|
||
## Development Environment Setup | ||
|
||
Please follow the instructions outlined in the [local development](https://docs.monosi.dev/docs/contributing/local-development) guide to get set up with a local instance of the project for development. | ||
|
||
## First-time contributors | ||
|
||
> **Note:** if you're a first-time contributor, we recommend that you [follow this tutorial](http://makeapullrequest.com/) to learn how to start contributing. | ||
- [Good first issues](https://github.com/monosidev/monosi/labels/good%20first%20issue) | ||
|
||
If you'd like to be assigned an issue, feel free to reach out on [Slack](https://monosi.dev/slack) or over email, or you can simply comment on an issue you'd like to work on. | ||
|
||
## Creating a PR | ||
|
||
Create a new pull request from your personal fork of the project if you want to make an update. We would prefer that you tag an existing issue or open a new issue describing the update first if possible! | ||
|
||
For now, please request Kevin (@unkrich) or Ivan (@iporollo) to review your PR. | ||
|
||
If you want to speak to us before doing lots of work, just ping us in [Slack](https://monosi.dev/slack) or email [[email protected]](mailto:[email protected]) | ||
|
||
## Questions | ||
|
||
Come say hi to us on [Slack](https://monosi.dev/slack)! 👋 | ||
|
||
Or if you prefer, email us at [[email protected]](mailto:[email protected]) — we're always happy to chat! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.