https://github.com/jamsocket/duckdb-demo

https://github.com/jamsocket/duckdb-demo

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/jamsocket/duckdb-demo
• Owner: jamsocket
• License: mit
• Created: 2022-01-22T16:15:28.000Z (almost 3 years ago)
• Default Branch: main
• Last Pushed: 2022-02-17T01:26:43.000Z (almost 3 years ago)
• Last Synced: 2024-05-17T06:49:53.983Z (7 months ago)
• Language: JavaScript
• Size: 67.3 MB
• Stars: 3
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# DuckDB Demo

## To develop:

From `/client`:

```sh

$ npm install

$ npm run watch

```

From `/server` (in separate tab):

```sh

$ npm install

$ npm run watch

```

Then visit [localhost:8080](http://localhost:8080)

## To build and run in a container:

```sh

$ docker build -t duckdb-demo .

$ docker run -dp 8080:8080 duckdb-demo

```

You can also pass environment variables to the container when running it:

```sh

$ docker run -dp 8080:8080 -e DEMO_DATA_SOURCE="https://storage.googleapis.com/jamsocket-demo-data/citibike-5M.parquet" duckdb-demo

```

Then visit [localhost:8080](http://localhost:8080)

## Data

This demo is set to use a large-ish dataset by default (~24MB). It downloads this dataset on the server process's initial run, which then caches it in the local filesystem so subsequent runs don't have to redownload the data. You can view this demo with even larger dataset by editing the `DEMO_DATA_SOURCE` environment variable, changing the `citibike-1M.parquet` filename to `citibike-5M.parquet` (`10M` and `25M` are also possible). If you are running the demo in a docker container, you can set the `DEMO_DATA_SOURCE` by setting the environment variable in the `docker run` command. If you are running the demo outside of the container (e.g. if you are developing), you can edit the environment variable in `server/.env.default`.

-----

### To build (outside of container):

From `/client`:

```sh

$ npm install

$ npm run build

```

From `/server`:

```sh

$ npm install

$ npm run build

```

### To run outside of container:

From `/server`:

```sh

$ npm start

```