Realtime Database

Since v2.3.0

Workspaces, dashboards, files and sync

A workspace saves the open tabs of a Realtime Database, so you can open them again in one click. Four Realtime Database widgets bring a node (as a value or a list), an aggregation, a chart or a top list to your dashboards. Workspaces, queries and dashboards travel as .fuego files, and settings sync carries your Realtime Database settings to your other computers.

Workspaces

A workspace is a saved set of tabs (from 1 to 10 tabs, up to 100 workspaces per database) of one Realtime Database. Each tab keeps its node, view, query, search and anonymize setting, so a set of places you check every day opens again in one click. Workspaces work on every plan and change only when you explicitly save or update them.

Save a workspace

  1. Open the tabs you want to keep on the same database.
  2. In the page’s Workspaces menu, choose Save tabs of {instance} as workspace….
  3. Give it a Name (up to 120 characters), an optional Icon and color, and untick any tabs to leave out under Tabs to save.
  4. Optionally turn on Keep on this computer only so it is never synced.
  5. Click Save.

Open and manage workspaces

  • Choose a workspace in the Workspaces menu (or in the database menu / command palette, or with fuego rtdb workspace open on the command line) to replace the open tabs of its database, or choose Add to open tabs ▸ to append them after the database’s open tabs (up to 10 tabs per database).
  • Every tab in a workspace opens as Admin, and follows Live only when Live on by default is on and your plan includes Live.
  • Update “{name}” from open tabs updates the active workspace; Manage workspaces… lets you star, edit, Share as file… or delete workspaces, and Import from file… imports a .fuego workspace file.

Dashboard widgets

A dashboard can show Realtime Database data next to Firestore data. The widget picker’s Realtime Database group offers four widgets on every plan:

WidgetWhat it shows
Realtime Database nodeOne node, shown as you choose under Display: Value (the value of the node) or List (its children as a table, 1–100 rows, optionally filtered by a query)
Realtime Database aggregationA Count, Sum or Average over the children of a node (up to 9,999 children), with optional period or target comparison
Realtime Database chartAn aggregation grouped by a child, as Bars, Line, Pie or Donut
Realtime Database top listThe top groups of an aggregation, ordered highest or lowest first

A chart or a top list groups the children of its node by A value inside each child (a child path such as status or address/city) or by Each child’s key: one group per child, named after its key. The second fits a node that already holds totals, such as /totals/<shop>/amount: set Sum of amount grouped by each child’s key to rank the shops.

Shown as a Value, a node that holds children is a tree of its keys: click a child that holds children to see them in place, as deep as the data goes, with nothing more read. Hover a row and click its button, or double-click the row, to open that node in the Realtime Database page; shown as a List, double-click a row of the table.

A widget’s header shows its title and, below it, the path it reads (cut at its start when it is too long, so the last keys stay readable). A widget with no title of its own is named after the last key of its path, or after its database at the root; a Realtime Database aggregation is named after what it computes, such as Sum of total, Average of price or Number of children.

Each widget reads one Database and one Path (as Admin), and refreshes from Every 30 seconds to Every 15 minutes (default Every minute, only while the dashboard is shown and not being edited, stopping after 15 minutes without input). Once a widget has read, its settings show how much each refresh downloads.

Live on a widget

On a paid plan, the Realtime Database node widget, shown as a value or as a list, can follow changes live with Live in the widget header (Live on this computer in its settings). It counts toward the 5 live streams per database, stops after 15 minutes without input, and is stored per computer (never synced or written to shared dashboard files).

Files

These .fuego files hold Realtime Database content and require Fuego 2.3.0 or later:

See Windows, links and notifications for how .fuego files work.

Copy a Fuego link to open a Realtime Database location from a ticket, a chat or a terminal:

  • Copy ▸ Fuego link in a node’s menu copies fuego://rtdb/my-project/my-project-default-rtdb/orders.
  • Copy link in the database menu copies the link to the database’s root.
  • fuego://rtdb/my-project/my-project-default-rtdb?workspace=… (printed by fuego rtdb workspace open <name> --print) opens a saved workspace.

Sync

With settings sync (a paid plan) enabled for a project, Fuego syncs its Realtime Database settings in a dedicated remote object (_fuego/<project>/rtdb-sync.yml in Storage or _fuego/<project>/rtdb/sync in Firestore) alongside your Firestore settings:

  • Synced: workspaces (unless kept on this computer only), saved queries, JSON schemas, row previews, paths/databases kept read-only in Fuego, database display names/order/hidden state, the 10 newest applied rules history entries, saved job dialog settings, and databases added by URL (which arrive as Unverified until confirmed on the receiving computer).
  • Kept on each computer only: private workspaces, a widget’s Live on this computer, the job dialog’s Ask Firebase not to run database triggers choice, all settings of an emulator project, and settings for databases a team sublicense does not allow.

Older versions of Fuego ignore the Realtime Database sync object without modifying it, and render Realtime Database widgets on a synced dashboard as placeholder cards without losing them on save.