tinysqlpage

tinySQL Page Server (tinysqlpage)

Part of tinySQL. See the root guide for supported SQL and the command index for other serving options.

An HTTP server that renders SQL-driven web pages. Each URL path maps to a .sql file in a pages directory; result sets are converted into HTML components (hero banner, stat cards, data table, text blocks) and served through a customisable template.

Build and run

go build -o tinysqlpage ./cmd/tinysqlpage

# bundled sample pages and seed data
./tinysqlpage

./tinysqlpage \
  -addr :8080 \
  -pages ./cmd/tinysqlpage/pages \
  -seed  ./cmd/tinysqlpage/sample_data.sql

The server has no built-in authentication. Keep it on the default loopback address for local use, or put authentication and HTTPS in front of it before serving pages remotely. Treat page definitions, templates, CSS, and seed SQL as trusted deployment input.

Flags

How it works

1. At startup, -seed SQL populates the in-memory database.
2. GET /some/path loads <pages-dir>/some/path.sql.
3. Each statement runs; result sets with a component column become HTML components.
4. Components are assembled and rendered through the HTML template.

Each request uses the caller's context and the configured timeout, so a cancelled client connection or a slow query does not keep rendering work alive. The page shell is parsed once on first use and the compiled, concurrency-safe template is reused for subsequent requests.

Navigation links are auto-generated from the .sql files in the pages directory. Labels, ordering and page title come from SQL comment front-matter.

Component types

Example page (pages/index.sql)

-- nav_label: Home
-- nav_order: 0
-- title: Sales Dashboard
SELECT 'hero' AS component, 'My Dashboard' AS title, 'Powered by tinySQL' AS subtitle;

SELECT 'stat_list' AS component,
       'Overview' AS title,
       department AS label,
       COUNT(*) AS value
FROM employees
GROUP BY department;

SELECT 'table' AS component, 'Recent Orders' AS title,
       id, customer, amount, created_at
FROM orders
ORDER BY created_at DESC
LIMIT 10;

Endpoints

Custom template

Pass -template path/to/page.html. The template is parsed with Go's html/template and receives:

<!DOCTYPE html>
<html>
<head><title>{{.Title}}</title><style>{{.Styles}}</style></head>
<body>
  <nav>{{.Nav}}</nav>
  <main>{{.Body}}</main>
</body>
</html>

Legacy {{TITLE}}, {{STYLES}}, {{NAV}} and {{BODY}} placeholders are rewritten to the fields above before parsing.