add dashboard for extension downloads

Author: c-herrewijn

.gitignore

@@ -1,4 +1,5 @@
 *.duckdb
 *.wal
 .env
+.vscode
 /evidence/.evidence/customization/.profile.json

README.md

@@ -70,7 +70,9 @@ Therfore (for now) there are 2 build steps:
 
 Steps to define a new source:
 - initial step to create a new source, see: https://docs.evidence.dev/core-concepts/data-sources/duckdb/
-- update `./scripts/generate_sources.sh` to make sure a `.duckdb` is created in this subdirectory with all data required for the dashboard
+    - run `make dev` to spawn the front-end
+    - following the steps in the link above will create a subdirectory under `./evidence/sources`
+- update `./scripts/generate_sources.sh` to make sure a `.duckdb` file is created in this subdirectory with all data required for the dashboard
 - add one or more `.sql` files to select the data relevant for the dashboard
 
 

evidence/pages/extension-downloads.md

@@ -0,0 +1,40 @@
+---
+title: Extension Downloads
+---
+
+```sql extensions
+  select
+      extension_name as extension
+  from extension_downloads.extension_downloads
+  group by extension
+  order by extension
+```
+<Dropdown data={extensions} name=extension value=extension>
+    <DropdownOption value="%" valueLabel="All Extensions"/>
+</Dropdown>
+
+<Dropdown name=year>
+    <DropdownOption value=2025/>
+    <DropdownOption value=2024/>
+</Dropdown>
+
+
+```sql extension_downloads
+  select
+      week,
+      downloads,
+      extension_name as extension
+  from extension_downloads.extension_downloads
+  where year = ${inputs.year.value}
+  and extension like '${inputs.extension.value}'
+  group by all
+  order by extension desc
+```
+
+<BarChart
+    data={extension_downloads}
+    title="Extension Downloads per week, {inputs.extension.label}"
+    x=week
+    y=downloads
+    series=extension
+/>

evidence/sources/extension_downloads/connection.yaml

@@ -0,0 +1,5 @@
+# This file was automatically generated
+name: extension_downloads
+type: duckdb
+options:
+  filename: extension_downloads.duckdb

evidence/sources/extension_downloads/extension_downloads.sql

@@ -0,0 +1 @@
+select * from extension_downloads

scripts/generate_sources.sh

@@ -15,7 +15,7 @@ if [ -z "$DUCKLAKE_USER" ];         then echo "Error: DUCKLAKE_USER is not set."
 if [ -z "$DUCKLAKE_DB_PASSWORD" ];  then echo "Error: DUCKLAKE_DB_PASSWORD is not set."; exit 1; fi
 
 
-duckdb ./evidence/sources/ci_metrics/ci_metrics.duckdb -c "
+duckdb -c "
 INSTALL ducklake;
 INSTALL postgres;
 
@@ -34,7 +34,13 @@ ATTACH 'ducklake:postgres:dbname=ducklake_catalog
     AS my_ducklake
     (DATA_PATH '$DUCKLAKE_S3_BUCKET', READ_ONLY);
 
+ATTACH './evidence/sources/ci_metrics/ci_metrics.duckdb' AS ci_workflows_db;
+USE ci_workflows_db;
 CREATE OR REPLACE TABLE ci_workflows AS FROM my_ducklake.ci_workflows;
 CREATE OR REPLACE TABLE ci_runs AS FROM my_ducklake.ci_runs;
 CREATE OR REPLACE TABLE ci_jobs AS FROM my_ducklake.ci_jobs;
+
+ATTACH './evidence/sources/extension_downloads/extension_downloads.duckdb' AS extension_downloads_db;
+USE extension_downloads_db;
+CREATE OR REPLACE TABLE extension_downloads AS FROM my_ducklake.extension_downloads;
 "