{{ message }}
Repository navigation
feat: Make the dev folder default behavior - #43
Merged
Merged
Conversation
Adds this runtime's own `devFolder` query parameter to `POST /v2/actors/:actorId/runs`. `devFolder=false` starts that one run from the built image alone, leaving the Actor's registered local dev folder untouched; the run log records the skip. Absent or any other value keeps today's behaviour, so real-platform clients are unaffected. This is what lets `apify call --no-dev-folder` turn the live folder off for a single run while `apify push` registers it by default. Also documents the CLI's automatic registration flow in the README, CLAUDE.MD and the specs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Reads the Actor's registered dev folder without changing it - the same envelope POST returns. `apify call` asks this before a run against the runtime to warn that the run will use the local folder rather than the built image alone. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
…iour only Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Pijukatel
changed the title
…tion Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
The previous case leaves a locally compiled dist/ in the temp Actor dir. apify push uploads it (no .gitignore there) and Docker's API build, which never sees .dockerignore, copies it over the builder stage's output - so the image carried the edited marker and the devFolder=false run could not prove it ran from the image. Podman applies .dockerignore server-side, which is why only the docker leg failed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
…ection When the registered dev folder is mounted, the run log starts with a delimited section naming the folder and warning that the run uses local source files, that compiled Actors need a local build first, and that `apify call --no-dev-folder` runs from the image. Absent when nothing local-only applies. Drops the GET /actor-runtime/dev-folder read-back, which only existed for a CLI-side banner that this replaces. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
…ver mount line Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X
Pijukatel
added a commit
to apify/apify-cli
that referenced
this pull request
Sep 10, 2026
Actors running through local actor runtime will by default work in local dev folder mode. Depends on: apify/actor-runtime#43 --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a read-only
GETendpoint for the dev folder registration and implements a per-run opt-out mechanism via?devFolder=falsequery parameter, allowing users to skip the dev folder mount for individual runs without clearing the registration.Key Changes
GET /actor-runtime/dev-folder/:actorIdendpoint - allows reading the current dev folder registration without modifying it; returns the same response format asPOSTand requires the same authentication/ownership scoping?devFolder=false- addeddevFolderoption toStartRunOptionsthat skips the bind mount for a single run when set tofalse, while leaving the Actor's registration untouched--no-dev-folderflag forapify calland the underlying?devFolder=falsequery parameterGETendpoint and the per-run opt-out behavior, covering edge cases like unregistered actors and parameter variationsImplementation Details
GETendpoint reuses the existingdevFolderStatus()helper to maintain consistent response formattingrunInBackground()checksoptions.devFolder === falseto determine whether to apply the mount, preserving the default behavior when the parameter is absent or any other valueapi.md,actor-driver.md, and user-facing docs (README.md,CLAUDE.MD)https://claude.ai/code/session_01TQMu5bht6poYGSeBYG1m7X