Repo says the repo is for learning.

But for a new user, the code-base is kinda a lot to grasp. Should we add a step-step tutorial on how to setup this on a blank Meltano project?

This isn't a priority, per se, but I just want to log that one nice feature is the ability to publish the Evidence report as a static webpage.

I have an example published from the MeltanoLabs fork here:

• GitHub CI Workflow File: https://github.com/MeltanoLabs/jaffle-shop-template/blob/main/.github/workflows/bi_publish.yml
• Example Publish: https://meltanolabs.github.io/jaffle-shop-template/

There's an outstanding bug - only affecting subpages, and only from non-root URLs - and it looks like this mat be fixed in a future Evidence release:

• meltano#6

My PR from the fork is here (meltano#5), and I updated that PR with some post-merge learnings and action items:

Update: There were some post-merge updates to resolve additional issues:

• Hotfix on reports for relative report paths from non-root host url: meltano@a1d0ffe
• My latest version of the GitHub Pages deploy workflow: https://github.com/MeltanoLabs/jaffle-shop-template/blob/main/.github/workflows/bi_publish.yml
• Remaining issue with hosting from non-root URL: meltano#6

Note

My implementation biases towards GitHub Pages because it doesn't require any external service signup. But it's worth noticing that other options like Vercel and Netflify would be an easier solve in regards to the above issues, since they do not have the issue with non-root publish URL. For a template project, there are still good reasons to prefer GitHub Pages - but if anyone wants a near-term solve, the other providers would likely have fewer sharp edges.

Thank you for creating this useful project!

I tried this today and the duckdb file was created by python duckdb 0.8.0 and failed to load in js duckdb 0.7.1.

I think we need to pin all DuckDB versions in this project (to 0.7.1 now).