pocketbase /

PocketBase

Live map
View repository
Snapshotmaster · 5d217dd

HTTP routes apply collection rules and hooks around record models, SQLite transactions, authentication, files, and subscriptions.

Click a building or route
Choose a path

Authenticate, run hooks, persist a record, and publish its change.

System map8 components · 8 connections
130%
PocketBase: one server wraps a realtime SQLite backend architectureStart at the serve command, enter API routing, then follow a record through auth, hooks, SQLite, files, and realtime delivery.application and server…credentials or tokenrequest and operation …validated record mutat…model fields and trans…collection action and …AuthenticationServe commandAPI routesApp events& hooksFile storageRecord modelRealtimebrokerSQLite access
Connections
BuildingsEntryServiceComputeStorageRuntimeToolingExternal

Terms, in plain English

CollectionA runtime-defined schema and rule set whose rows are PocketBase records.

How to study this repo

  1. 1
    Route one request

    Follow record creation from the router into its request event.

  2. 2
    Persist safely

    Trace record validation and save behavior through a database transaction.

  3. 3
    Notify a subscriber

    See how a successful mutation becomes an authorized realtime message.