Lowdefy modules — MongoDB

A set of reusable Lowdefy modules backed by MongoDB — authentication, user admin, contacts, companies, file attachments, audit events, notifications, and more.

Requires Lowdefy 7. Pin module sources to a release tag.

Full documentation: docs/

Quick start

Declare the app's slug on the root of your lowdefy.yaml, then add modules to the modules array, pinning each to a tagged release:

name: My App
slug: my-app # kebab-case; modules scope themselves to it via `_build.app: slug`

modules:
  - id: events
    source: "github:lowdefy/modules-mongodb/modules/events@v1.4.1"

  - id: layout
    source: "github:lowdefy/modules-mongodb/modules/layout@v1.4.1"

  - id: user-account
    source: "github:lowdefy/modules-mongodb/modules/user-account@v1.4.1"

  - id: notifications
    source: "github:lowdefy/modules-mongodb/modules/notifications@v1.4.1"

The slug is declared once and read by every module that scopes data per app — there is no per-module app-name var. Where a value needs it explicitly, use the operator; the audit stamp's app attribution is the common case (the stored field stays named app_name, its value is the slug):

- id: events
  source: "github:lowdefy/modules-mongodb/modules/events@v1.4.1"
  vars:
    change_stamp:
      timestamp:
        _date: now
      user:
        name:
          _user: profile.name
        id:
          _user: id
      app_name:
        _build.app: slug

The minimum set for an authenticated app is layout + events + user-account + notifications. See docs/index.md for the full module list, dependency graph, and "what to use when" guide, and docs/shared/app-name.md for how the slug scopes stored data.

Documentation

See docs/CONTRIBUTING.md for the docs front-matter and authoring schema. Release notes live in CHANGELOG.md.