Skip to content

Functions

HomeCloud Functions are managed serverless compute units — the platform equivalent of AWS Lambda. You author Python 3.12 handlers in a VS Code–class console workspace, deploy immutable versions, and invoke them synchronously through the control plane (the warm runtime lives on the Functions data plane).

Create

  1. Open Console → Functions.
  2. Create function — choose a DNS-compatible name, handler (default main.handler), memory, and timeout.
  3. The platform seeds an empty workspace with main.py.

Permissions: function.create (falls back to resources.create in the console when role matrices align).

Code workspace

The Code tab is a multi-file editor:

  • Left file tree with VS-style file icons and role badges (Entrypoint / Runs / Asset / Edit only)
  • Multi-tab Monaco editor (Dark+/Light+ themes; optional theme override)
  • New file / new folder / rename / delete, autosave, Format, Outline, Problems, Search
  • Language mode follows extension (.py → Python, .json → JSON, .md → Markdown)

Working-tree files are stored per function until you deploy.

Language intelligence (IDE)

The Code editor uses a VS Code–class split:

Surface Path When
LSP (BasedPyright) WebSocket → Language Host on the API Interactive editing — hover, completion, diagnostics, semantic tokens
HTTP /language/analyze Control-plane analyze Build Preview, Deploy Strict, SDK / CI automation

While LSP is connected, the console does not call HTTP analyze on every autosave. Monaco keeps a stable file:///workspace/… model identity when LSP connects (no editor remount / flicker). Switching away from the Code tab keeps the workspace mounted so the Language Host session is reused.

Attached function layers are extracted into a shared language cache on the API (keyed by layer version) instead of unzipping into every edit-session temp directory.

Build & Deploy Preview

Open Build & Deploy Preview in the Code toolbar before deploying:

  • Runtime and Handler come from function configuration (source of truth)
  • Entrypoint is derived from the handler (main.handler → main.py)
  • File list shows included vs excluded paths with package size and warnings
  • Packaging excludes Markdown docs, .env secrets, and Python caches — the same rules Deploy uses
  • Deploy is blocked when validation fails (missing entrypoint or handler callable)
  • requirements.txt may appear as declared only (not installed in the package yet)

Pipeline: Workspace → Validate → Build Preview → Package → Deploy → Invoke.

Deploy

Deploy version packages the workspace with the shared packager into a new immutable function_version and updates $LATEST.

  • When Object Storage (SO) is available, the packaged artifact is referenced with an so:// URI (for example so://functions/{account}/{name}/v{n}.zip).
  • In local/dev mode the zip may be stored on the version row until SO is configured.

Rollback is available via the versions API (POST …/versions/{n}/rollback).

Invoke

From the Invocations tab:

  1. Edit the Event JSON payload.
  2. Click Invoke.
  3. Inspect result, status, duration, and logs.

The control plane orchestrates the call; production execution runs on homecloud-fn (POST /invoke with package + layers as base64 zips). Manual HTTP invoke URLs are shown on Overview when configured.

Triggers

Supported trigger types:

Type Use
manual Console / API test invoke
http HTTP binding / invoke URL
queue MQ (JetStream) consumer
cron Schedule expression

Create, enable/disable, and delete triggers from the Triggers tab.

Layers

Layers package shared dependencies (platform or account-scoped). Attach one or more layers on the Layers tab; layer artifacts also use so:// when published to Object Storage.

Layer layout for Python: include a top-level python/ directory (or the layer root is added to PYTHONPATH).

Runtime notes

  • Runtime: Python 3.12
  • Handler form: module.callable (for example main.handler)
  • Execution: subprocess sandbox with timeout; memory is a soft limit advertised to the handler context
  • Data-plane host: fn.holab.abrdns.com (internal invoke may use X-Homecloud-Internal-Token when configured)