Deployment

Jamrock supports multiple runtimes. Choose the one that fits your infrastructure.

Supported Runtimes

Building for Production

Build your application before deployment:

jamrock build

This creates a dist/ directory with compiled templates, bundled assets, and static files.

---

Running the Server

Use the ./bin/RUNTIME wrapper for your preferred runtime — the commands are identical across all three:

# Development (pick your poison)
./bin/node dev
./bin/deno dev
./bin/bun  dev

# Production
./bin/node build && ./bin/node serve

Docker

FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
RUN ./bin/node build
EXPOSE 3000
CMD ["./bin/node", "serve"]

---

GTK4 Desktop Apps

Build native desktop applications with GTK4 widgets:

# Development server
./bin/gjs serve --src playground

# Widget explorer
./bin/gjs explorer

Available Widgets

Layout: vstack, hstack, box, grid, scroll, overlay, stack, paned, expander, revealer, frame, center

Input: button, toggle, push, check, entry, search, spin, range, dropdown, color, font, file

Display: label, image, spinner, progress, level, calendar, clock, textview, listview, columnview, treeview

Example

<script>
  import { signal } from 'jamrock';
  let count = signal(0);
</script>

<vstack spacing="10">
  <label>Count: {$count}</label>
  <button onclick={() => count.value++}>Increment</button>
</vstack>

GTK4 apps use the same component syntax as web apps, but with GTK widget elements instead of HTML.

Layout Utilities

The class attribute on GTK widgets expands shorthand tokens into native widget properties — similar to Tailwind, but mapping directly to GTK:

Any unrecognized token is passed through as a CSS class name via add_css_class. You can mix both in one attribute:

<vstack class="hx sp-2">
  <label class="ha-center my-widget-label">Hello</label>
</vstack>

---

Static Export

Pre-render all routes to static HTML for hosting on GitHub Pages, Netlify, or any CDN:

jamrock build && jamrock write

---

Session Storage

For production, configure a persistent session store:

export default {
  redis: {
    url: process.env.REDIS_URL,
  },
};

The default memory store is fine for development. Use Redis for any multi-instance or persistent production setup.

Health Checks

Add a health endpoint in your +server.mjs:

export default {
  ['GET /health']() {
    return Response.json({ status: 'ok' });
  },
};