machhub

Build an Angular app on MACHHUB — a client-only SPA that talks to MACHHUB through the SDK with zero-config `Initialize()`. Covers initializing the SDK before bootstrap, an auth service and functional route guard, signal-based collection and tag services, and building for upload. Use for any Angular frontend that reads or writes MACHHUB data.

Generate valid MACHHUB Collection schemas in JSON format with proper data types, relations, indexes, and onDelete behaviors for database import and schema management.

Generate and validate MACHHUB Data Bridge configuration in JSON for import — MySQL connections, outbound (egress) routes from UNS topics to database tables, inbound (ingress) routes polling tables into UNS topics, column mappings, write modes, watermarks and buffer policy.

Simple guide for users and AI on how to fill in the groups.json when importing group (role) assignments on the MACHHUB Permissions page or via the Designer extension. No technical knowledge required.

Run the MACHHUB SDK headless from a standalone Node script (no browser/UI) to read or write live backend data for one-off bulk ops, seeds, backfills, and audits. Use when an AI agent needs to query or mutate MACHHUB collections directly without going through the app - e.g. bulk-updating items, seeding flags from a spreadsheet, or fixing data in place.

Guide for users and AI on how to fill in a namespace JSON file for the Designer extension's Namespaces panel — the UNS topic tree (folders and tags) and each tag's historian settings. Covers what an upload applies to the running server and what it leaves alone.

Build a React app on MACHHUB — a client-only Vite SPA (or a Next.js static export) that talks to MACHHUB through the SDK with zero-config `Initialize()`. Covers the SDK provider, auth with `sdk.auth`, collection and realtime hooks, route guards, and building for upload. Use for any React or Next.js frontend that reads or writes MACHHUB data.

Build a Vue 3 app on MACHHUB — a client-only Vite SPA (or Nuxt with `ssr: false`, statically generated) that talks to MACHHUB through the SDK with zero-config `Initialize()`. Covers initializing before mount, auth composable and router guard, collection and tag composables, and building for upload. Use for any Vue or Nuxt frontend that reads or writes MACHHUB data.

Simple guide for users and AI on how to fill in the JSON when importing permission setups (features and scopes) on the MACHHUB Permissions page or via the Designer extension. No technical knowledge required.

Answer natural-language data questions about the LIVE MACHHUB runtime by writing and running TypeScript/Node against it. Use when the user asks to look up, find, list, count, filter, inspect, summarize, or report on records in a MACHHUB collection, tag, historian series, or process — e.g. "which items are inactive?", "how many open purchase orders?", "show low-stock locations", "what's the latest reading for tag X". Connects through the Designer runtime connection on :61888 (no credentials needed). READ-ONLY — never mutates data. Discovers schema from the runtime, runs a query, returns the answer.

Historian (time-series) reads with the MACHHUB SDK — latest values, time windows, aggregated CSV export — plus read-only Data Bridge queries (`sdk.bridge`) and calling server-side logic via Processes. Use for trends, charts, reports, exports, and reading an external SQL database from an app or process.

How to structure a MACHHUB frontend app — one SDK module, thin per-collection data modules, auth and tag hubs, and components that never touch the SDK directly. Covers the folder layout, typing records, error handling and testing. Use when starting a MACHHUB app or reorganizing one.

Log users in and out of a MACHHUB app with the SDK (`sdk.auth`) — login, logout, restoring a session on page load, the current user, JWT data, and password changes. Use whenever an app needs a login screen, a logged-in user, or a signed-out redirect.

Check what the logged-in MACHHUB user may do (`checkAction`, `checkPermission`), and administer users, groups and permissions through the SDK. Covers features, actions and scopes, how MACHHUB matches them, and which admin operations the SDK has and lacks.

Read and write MACHHUB collection records with the SDK — create, getAll, getOne, update, delete, count, filters (including inside JSON arrays), sorting, paging, expanding relations, and the record ID format. Use for any code that queries or changes collection data from an app.

Upload, replace, clear and download files in MACHHUB collection `file` fields with the SDK — single and multiple file fields, getting a file back as a Blob, showing images, and downloads. Use whenever a collection record carries an image, document or attachment.

Initialize the MACHHUB TypeScript SDK (`@machhub-dev/sdk-ts`). Browser apps hosted on MACHHUB call `Initialize()` with no arguments, and it works in local dev (through the Designer extension) and once deployed. Covers how that discovery works, the one-SDK-per-app rule, and the narrow case for explicit config with an API key (Node scripts and external services).

MACHHUB Processes: write, schedule, and execute Python or TypeScript code on the MACHHUB platform. Use when: configuring process triggers (cron, interval, tag_change, HTTP endpoint, manual), defining process inputs (tag reads, SQL queries) and outputs (SQL writes, tag writes), invoking a process from the frontend SDK, managing Python/npm package dependencies, or writing user code inside a Process (execute function context pattern).

Live tag values in a MACHHUB app — list tags, subscribe (with + and # wildcards), publish, and unsubscribe through `sdk.tag`, plus the SDK's one-handler-per-topic behaviour and a fan-out hub so several components can watch the same tag. Use for live dashboards, machine status, and writing setpoints.

Build a Svelte 5 + SvelteKit app on MACHHUB — a client-only SPA (adapter-static, ssr off) that talks to MACHHUB through the SDK with zero-config `Initialize()`. Covers SDK setup in the root layout, auth with `sdk.auth` and route guards, rune-based collection and realtime stores, and building for upload. Use for any Svelte or SvelteKit frontend that reads or writes MACHHUB data.