Skip to content

Conversation

Pijukatel
Copy link
Contributor

@Pijukatel Pijukatel commented Feb 25, 2025

Add small docs section about how to use force_cloud argument in local development.

Documents #412

@github-actions github-actions bot added this to the 109th sprint - Tooling team milestone Feb 25, 2025
@Pijukatel Pijukatel added documentation Improvements or additions to documentation. t-tooling Issues with this label are in the ownership of the tooling team. labels Feb 25, 2025
@Pijukatel Pijukatel marked this pull request as ready for review February 25, 2025 08:38
Copy link
Contributor

@vdusek vdusek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks


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
Copy link
Contributor

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?

Copy link
Member

@B4nan B4nan left a 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

@Pijukatel
Copy link
Contributor Author

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

Pijukatel and others added 2 commits February 25, 2025 12:47
Co-authored-by: Martin Adámek <banan23@gmail.com>
@Pijukatel Pijukatel requested review from janbuchar and B4nan February 25, 2025 12:00
@Pijukatel Pijukatel merged commit e61bb0f into master Feb 25, 2025
27 checks passed
@Pijukatel Pijukatel deleted the force-cloud-documentation branch February 25, 2025 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation. t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants