Using Community Logic

The Aerostack registry lets you install published community functions into your project with the CLI. For the full create → publish → consume flow, see Function Flow Overview.

Installing a function

Use the functions install command with either a slug (if unique) or username/slug:

aerostack functions install notes-module
# Or with author:
aerostack functions install alice/notes-module

When you use only a slug, the API resolves to a single published function (e.g. by popularity). Use username/slug when you want a specific author’s function.

What happens during installation?

The CLI fetches the install manifest from the registry and injects the function into your project:

Code download: Source files are written to services/<slug>/ (e.g. index.ts, optional README.md).
Project registration: The CLI updates aerostack.toml to register the new service.

You own the copied source and can edit it in your repo.

Updating an installed function

Because the function is copied as source into services/<slug>/, you can:

Edit the files directly to customize behavior.
To pull a newer version from the registry, run aerostack functions install <slug> or username/slug again; the CLI will overwrite the existing files in services/<slug>/ (ensure you don’t have uncommitted changes you need to keep).

Finding modules

Browse the Aerostack Hub to find published functions for:

Authentication: Social logins, OTP, and session management.
Payments: Stripe integration, subscription handling.
AI: Prompt templates, vector search integrations.
Utilities: Slugify, image processing, and data validation.

Function Flow Overview Publishing Overview