Skip to content

Daemons / Background Processes (under server) #9

@fbarrento

Description

@fbarrento

What to build

Daemons (called "Background Processes" in the OpenAPI spec) under /orgs/{org}/servers/{server}/background-processes/.... Independent of Sites/Deployments — can ship in parallel with #7 and the Deployments issue.

Endpoints (per docs/forge.openapi.json):

  • list, create, get, update, delete background processes
  • POST /orgs/{org}/servers/{server}/background-processes/{backgroundProcess}/actions (start/stop/restart)
  • GET /orgs/{org}/servers/{server}/background-processes/{backgroundProcess}/log

Source design: see project_sdk_design.md in the project's memory.

Acceptance criteria

  • Daemon DTO (or BackgroundProcess — pick the name closer to Forge's UI parlance; Forge users say "daemon")
  • CreateDaemonData, UpdateDaemonData, ListDaemonsOptions input DTOs
  • Request classes for CRUD + actions + log
  • DaemonsResource and DaemonResource
  • $forge->server($id)->daemons()->all() etc.
  • $forge->server($id)->daemon($id)->restart() (or equivalent action wrapper)
  • $forge->server($id)->daemon($id)->log(): string returns the raw log content
  • Tests
  • composer test green

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions