-
Notifications
You must be signed in to change notification settings - Fork 19
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
Enable running non-JS programs with apify run #271
Comments
This just occured to me, but... Why do we need the env-var injection if we don't have the non-JS SDKs that would read the env vars in the first place? I mean, the fact that the CLI injects And as far as We can't use the local env-vars for the simple read input -> run -> save output scenario. Or am I missing something? |
The main use-cases are probably API actions & proxy password |
Yeah, but you still need to know the env-vars and add them manually into your own code, so installing CLI is pretty much the same as installing a language specific env var manager. It would make a little more sense if the CLI was native, so you wouldn't need to install Node to install it. But if you're running Rust, it's probably easier to just use whatever Rust uses to inject 2 env vars than installing Node and CLI. |
You get the token & proxy password via |
It would be nice to use Apify CLI for non-JS programs for env vars injection (token + proxy password)
One example how it could look like:
apify run -p --command "cargo run"
(to run Rust program)The text was updated successfully, but these errors were encountered: