Skip to content
IDE for Presto
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Add architecture to Readme Apr 15, 2019
quix-backend unify execution events (#45) Apr 24, 2019
quix-frontend (frontend) dont forget to copy note name when cloning a notebook Apr 24, 2019
.env Change default DB_VOLUME_PATH Apr 17, 2019
.gitignore
.travis.yml add -DskipTests=true, fixes #39 (#43) Apr 24, 2019
LICENSE Initial commit Apr 14, 2019
README.md Add links to Presto Apr 23, 2019
docker-compose.yml Change backend port to avoid conflicts with Presto and other JVM appl… Apr 16, 2019

README.md

Quix

Build Status
Quix is a Web IDE for Presto.

It's your single point of truth and a shared space for your company's BI insights, with quick turnaround, interactive visual perspectives, and mixed data sources.

Disclaimer

Please note that this is a beta version of Quix which is still undergoing final testing before its official release.

Main features

  • Presto notes
  • Notebooks
  • Folders
  • DB-tree
  • Smart Editor

Requirements

Installation

All you need to do is to run Docker Compose:

docker-compose up
open http://localhost:3000

Configuration

Most of the configuration you'll need is done in .env configuration file.
By default, Quix works with demo Presto instance that runs inside Docker Compose.
To work with your real Presto DB, change PRESTO_API URL. Note that you need to specify full URL, including protocol, port and API version. For example: http://presto.my.domain:8181/v1

Quix also uses MySQL to store notebooks and other application data. Location of this data is specified by DB_VOLUME_PATH.
As an alternative, you may use external MySQL database, by specifying some of the following variables:

  • DB_NAME - defaults to Quix, must exist
  • DB_USER - defaults to root
  • DB_PASS - defaults to empty password
  • DB_HOST - defaults to db
  • DB_PORT - defaults to 3306

Architecture

Quix consists of three main elements:

  • Frontend to serve UI and manage notebooks persistence
  • Backend to communicate with Presto
  • DB to persist notebooks

Each component is run in a separate Docker container, and all of them are managed by a single Docker Compose configuration.

There's fourth Docker container which we provide that runs Presto inside Docker Compose, but it's for demonstration purposes only.

License

MIT

You can’t perform that action at this time.