-
Notifications
You must be signed in to change notification settings - Fork 15
docs: Add force_cloud argument documentation #415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
docs/03_concepts/03_storages.mdx
Outdated
|
||
Each dataset item, key-value store record, or request in a request queue is then stored in its own file in the storage folder. Dataset items and request queue requests are always JSON files, and key-value store records can be any file type, based on its content type. For example, the Actor input is typically stored in `storage/key_value_stores/default/INPUT.json`. | ||
|
||
## Local Actor run with non-local storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Could you also mention that the typical use is when you want to call another Actor and then access its default dataset/kvstore/rq?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this would likely deserve a note in the JS SDK docs too
Docs are structured differently there, but it is mentioned here: https://crawlee.dev/docs/deployment/apify-platform#using-platform-storage-in-a-local-actor |
Co-authored-by: Martin Adámek <[email protected]>
Add small docs section about how to use
force_cloud
argument in local development.Documents #412