Skip to content

Commit af49750

Browse files
committed
Missed commits
1 parent 387a3c4 commit af49750

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

articles/azure-functions/functions-develop-local.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -85,12 +85,12 @@ Other files in the project depend on your language and specific functions. For m
8585

8686
### Local settings file
8787

88-
The local.settings.json file stores app settings and settings used by local development tools. Settings in the local.settings.json file are used only when you're running your project locally. When you publish your project to Azure, be sure to also add any required settings to the app settings for the function app.
88+
The `local.settings.json` file stores app settings and settings used by local development tools. Settings in the `local.settings.json` file are used only when you're running your project locally. When you publish your project to Azure, be sure to also add any required settings to the app settings for the function app.
8989

9090
> [!IMPORTANT]
91-
> Because the local.settings.json may contain secrets, such as connection strings, you should never store it in a remote repository. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.
91+
> Because the `local.settings.json` file might contain secrets, such as connection strings, you should never store it in a remote repository. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.
9292
93-
The **local.settings.json** file has this structure:
93+
The `local.settings.json` file has this structure:
9494

9595
```json
9696
{

articles/azure-functions/functions-run-local.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,6 @@ npm install
230230
npm start
231231
```
232232

233-
The Azure Functions CLI will find functions using the value of the `main` key in your `project.json` file. For multiple functions, use a glob as in the default: `dist/src/functions/*.js`.
234233
::: zone-end
235234
::: zone pivot="programming-language-python"
236235
This command must be [run in a virtual environment](./create-first-function-cli-python.md).
@@ -246,6 +245,10 @@ Job host started
246245
Http Function MyHttpTrigger: http://localhost:7071/api/MyHttpTrigger
247246
</pre>
248247

248+
::: zone pivot="programming-language-typescript,programming-language-javascript"
249+
How your functions are loaded depends on your project configuration. To learn more, see [Registering a function](functions-reference-node.md#registering-a-function).
250+
::: zone-end
251+
249252
Keep in mind the following considerations when running your functions locally:
250253

251254
+ By default, authorization isn't enforced locally for HTTP endpoints. This means that all local HTTP requests are handled as `authLevel = "anonymous"`. For more information, see [Authorization level](functions-bindings-http-webhook-trigger.md#http-auth). You can use the `--enableAuth` option to require authorization when running locally. For more information, see [`func start`](./functions-core-tools-reference.md?tabs=v2#func-start)

0 commit comments

Comments
 (0)