feat: Made dev folder for Actor runtime default by Pijukatel · Pull Request #1415 · apify/apify-cli · GitHub
Skip to content

feat: Made dev folder for Actor runtime default - #1415

Merged
Pijukatel merged 6 commits into
actor-runtimefrom
claude/focused-noether-q8h4op
Sep 10, 2026
Merged

Pijukatel merged 6 commits into
actor-runtimefrom
claude/focused-noether-q8h4op

Conversation

@Pijukatel

Copy link
Copy Markdown
Contributor

Actors running through local actor runtime will by default work in local dev folder mode.

Depends on: apify/actor-runtime#43

Pijukatel and others added 6 commits September 9, 2026 09:35
When the CLI is pointed at a local Actor runtime (APIFY_CLIENT_BASE_URL is not the Apify
cloud), `apify push` now registers the pushed directory as the Actor's live dev folder via
the runtime's `POST /actor-runtime/dev-folder/:actorId` right after uploading, so every
later `apify call` mounts the local source over the built image with no extra step.

- `apify push --no-dev-folder` skips the registration and clears any earlier one.
- `apify call --no-dev-folder` runs once from the built image alone by sending the
  runtime's `?devFolder=false` run-start extension; the registration stays.
- Against the Apify platform neither flag sends a request: push is silent, call warns
  once that the flag is ignored. A non-cloud target that 404s the endpoint is treated as
  "not a runtime" and skipped with a debug log only.
- `apify push --json` reports `localDevFolder` when a runtime answered.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
…er call

Verified end to end against a runtime built from the branch: the bind mount hides the
image's compiled dist/, so a TypeScript Actor's first `apify call` after an automatic
registration fails until `npm run build` has run locally. The push message now says so.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
…cal source

Against a local Actor runtime, `apify call` now reads the Actor's registered dev folder
(`GET /actor-runtime/dev-folder/:actorId`) and, when one is set and --no-dev-folder was
not passed, prints a red banner naming the folder, the local-compile requirement for
TypeScript Actors, and the `--no-dev-folder` way out. Older runtimes without the GET
answer 404 and get no banner.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Against a local Actor runtime, push always registers the pushed directory. The only
user-facing switch is 'apify call --no-dev-folder'.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
The runtime now opens the run log with a "Local Actor runtime" section carrying the
warning, which apify call streams anyway. The CLI keeps only --no-dev-folder and the
automatic registration on push.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Smaller registration helper with a two-state result, no Windows path guessing, no
localDevFolder in the push output, and only the tests that pin behaviour.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
@Pijukatel
Pijukatel marked this pull request as ready for review September 10, 2026 15:53
@Pijukatel
Pijukatel merged commit 93205b6 into actor-runtime Sep 10, 2026
@Pijukatel
Pijukatel deleted the claude/focused-noether-q8h4op branch September 10, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants