How can I run an Actor local with Actor.config inputs?

I'd like run the next code localy

// Initialize the Apify SDK
await Actor.init();
const privateKey: string = Actor.config.get('private_key');
const clientEmail: string = Actor.config.get('client_email');

// Initialize the Apify SDK
await Actor.init();
const privateKey: string = Actor.config.get('private_key');
const clientEmail: string = Actor.config.get('client_email');

But

privateKey

privateKey

undefined

undefined

I expected to use it like

npx apify-cli run

npx apify-cli run

but nothing.

Any suggestion?

Alex IOP•6/21/24, 7:41 PM

To run an Actor locally and read from , you need to ensure your local environment mimics the remote environment where the is available. The file is typically used in the Apify platform, so running it locally requires a few extra steps to simulate this environment.

Here's how you can set it up:

Create Locally:
Create a local file in the root directory of your project with the required inputs. For example:

**Set Up Local Environment**:Create a local script to read this configuration file and use it as the input for your actor.
**Modify the Script to Read Local Configuration**:Adjust your script to read the configuration file locally when not running on the Apify platform.

Alex IOP•6/21/24, 7:41 PM

Here's an updated script that can run locally:

Alex IOP•6/21/24, 7:42 PM

Step-by-Step Explanation:

**Environment Detection**:
- The script checks if it's running in a production environment (assuming is set to on the Apify platform). If not, it reads the file locally.
**Local Configuration Reading**:
- When running locally, the script reads the file from the project's root directory using Node.js's module.
**Crawler Setup and Execution**:
- The rest of the script remains the same, setting up and running the
```
PlaywrightCrawler
```
```
PlaywrightCrawler
```
  with the configuration read from the input.

### Notes:

Ensure your file is correctly formatted and available in the root directory of your project when running locally.
You can adjust the logic to handle different configurations and input structures as needed.
Remember to install the necessary dependencies (, , and module if not already available).

This approach should allow you to run your actor both locally and remotely with the same codebase, adjusting only the way the configuration is read.

Alex IOP•6/21/24, 7:42 PM

Is this optimal approach?

Pepa J•6/25/24, 6:11 AM

Hi @Alex I I am little bit confused, seems to me that you use the term

config

config

in the same way as

You may create the file locally as described here No INPUTS.json in puppeteer js template
Also if you generate your project via crawlee-cli and run it via it should create this folder/input structure automatically for you.