You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a source flag/env option to add flexibility to execution path (#53)
* new: Adds source flag for flexibility to execute different paths
* Add the option flag/env to README.md
* fix: env vars must start with FUNCTION_ prefix
`--port` | `PORT` | The port on which the Functions Framework listens for requests. Default: `8080`
148
148
`--target` | `FUNCTION_TARGET` | The name of the exported function to be invoked in response to requests. Default: `function`
149
149
`--signature-type` | `FUNCTION_SIGNATURE_TYPE` | The signature used when writing your function. Controls unmarshalling rules and determines which arguments are used to invoke your function. Default: `http`; accepted values: `http` or `event`
150
+
`--source` | `FUNCTION_SOURCE` | The path of your project directory where you want to start. Functions framework always look only at root path, setting this option will look for your function in any other folder. Default: `/`
150
151
151
152
You can set command-line flags in your `package.json` via the `start` script.
0 commit comments