Skip to content

Add ensureBackgroundProcess + ensureScheduledJob methods (recipes must stop being the fallback) #4

Description

@nathanworking

Policy (Nathan 2026-07-28): recipes are effectively banned — every run emails a report and one-off recipes litter the org; recurring server work must be Forge-native so it's dashboard-visible. The v2 endpoints exist and were verified live against org goodcraft, server 1195166: POST /orgs/{org}/servers/{id}/background-processes with {name, command, user, directory, processes} (supervisor-backed; 'The name field is required' if name omitted) and POST /orgs/{org}/servers/{id}/scheduled-jobs with {name, command, user, frequency: 'custom', cron}. GETs on both list existing entries. Please add idempotent ensureBackgroundProcess / ensureScheduledJob methods (match on name; create or update) so queue workers, schedulers, and backup crons never need recipes or hand-rolled /etc/cron.d + supervisor confs. Reference implementations created manually 2026-07-28: background-process 977843 (ballast-queue), scheduled-jobs 2090669/2090670.

Upstream repository: https://github.com/nathanworking/swamp-forge-provision

Environment

  • Extension: @goodcraft/forge@2026.07.21.2
  • swamp: 20260721.174127.0-sha.0e77b06b
  • OS: darwin (aarch64)
  • Deno: 2.8.3
  • Shell: /bin/zsh

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions