Conversation
Builds on portal mode (already on main). Datasets become first-class named entities — a CSV is uploaded, converted to Parquet, and stored in object storage (a local folder, or Garage/S3 via the optional .[portal] extra); charts reference them by name. The dashboard YAML drops its datasets: block, and charts read Parquet via lazy scans with projection + predicate pushdown. A Datasets gallery tab handles upload / replace / rename / remove, with a delete-guard and cascade-rename. Local paths mode (FIREFLYER_PATHS) is a non-portal way to manage many dashboards + datasets against your own filesystem: each Docker-mapped folder is a switchable "path" — dashboards as <path>/dashboards/*.yaml, datasets in an isolated per-path blob store — seeded with a demo path on first run, meant to be kept in git and deployed by a coming CLI/API (a GitOps workflow; datasets stay server-side). Editor and gallery navigation reworked: a Dashboards | Datasets switch on the list pages, a path dropdown (local paths mode), and a shared back button on selected items. Bumps to 0.5.0.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Datasets become first-class named entities — a CSV is uploaded, converted to Parquet, and stored in object storage (a local folder, or Garage/S3 via the optional .[portal] extra); charts reference them by name. The dashboard YAML drops its datasets: block, and charts read Parquet via lazy scans with projection + predicate pushdown. A Datasets gallery tab handles upload / replace / rename / remove, with a delete-guard and cascade-rename.
Portal mode (opt-in, FIREFLYER_PORTAL) stores many dashboards in a database with a gallery + a simple login, reusing the stateless editor unchanged. Local paths mode (FIREFLYER_PATHS) is the non-portal equivalent against your own filesystem: each Docker-mapped folder is a switchable "path" — dashboards as /dashboards/*.yaml, datasets in an isolated per-path blob store — seeded with a demo path on first run, meant to be kept in git and deployed by a coming CLI/API (a GitOps workflow; datasets stay server-side).
Editor and gallery navigation reworked: a Dashboards | Datasets switch on the list pages, a path dropdown (local paths mode), and a shared back button on selected items. Bumps to 0.5.0.