add instructions for ZUPLO_LOG_LEVEL

.tool-versions

@@ -1 +1,2 @@
-nodejs 22.13.1
+nodejs 22.13.1
+local nodejs 23.9.0

docs/articles/cloudflare-settings.md

@@ -3,11 +3,11 @@ title: Zuplo and Cloudflare Settings
 sidebar_label: Cloudflare Settings
 ---
 
-Most fully managed Zuplo environemnts are deployed behind Cloudflare's Web Application
-Firewall, DDoS protection, Bot Detection, and SSL termination. The combination
-of Cloudflare's network infrastructure and Zuplo's API Gateway help provide
-critical security and performance capabilities to your API all with zero custom
-configuration.
+Most fully managed Zuplo environemnts are deployed behind Cloudflare's Web
+Application Firewall, DDoS protection, Bot Detection, and SSL termination. The
+combination of Cloudflare's network infrastructure and Zuplo's API Gateway help
+provide critical security and performance capabilities to your API all with zero
+custom configuration.
 
 ## Web Application Firewall Rules
 

docs/articles/dev-portal-setup.md

@@ -39,6 +39,10 @@ my-project/
 - **docs/dev-portal.json** - This is the primary configuration for your
   developer portal with customization for the favicon, authentication settings,
   etc. [Documentation](./dev-portal-json.md)
+- **ZUPLO_LOG_LEVEL** - This environment variable configures the log level in
+  your Zuplo portal to control which logs are displayed. To show only errors or
+  warnings, set ZUPLO_LOG_LEVEL to error or warn in the Settings tab under the
+  Environment Variables section.
 
 :::caution
 

docs/articles/log-plugin-azure-blob.md

@@ -17,7 +17,6 @@ The plugin is configured in the [Runtime Extensions](./runtime-extensions.md)
 file `zuplo.runtime.ts`:
 
 ```ts
-
 // The interface that describes the rows
 // in the output
 interface AzureBlobLogEntry {
@@ -31,28 +30,32 @@ interface AzureBlobLogEntry {
 }
 
 // The function that creates an entry
-async function generateLogEntry(response: Response, request: ZuploRequest, context: ZuploContext) {
+async function generateLogEntry(
+  response: Response,
+  request: ZuploRequest,
+  context: ZuploContext,
+) {
   const entry: AzureBlobLogEntry = {
     timestamp: new Date().toISOString(),
     url: request.url,
     method: request.method,
     status: response.status,
     statusText: response.statusText,
     sub: request.user?.sub ?? null,
-    contentLength: request.headers.get("content-length")
+    contentLength: request.headers.get("content-length"),
   };
   return entry;
 }
 
 // Add the plugin - use a SAS URL
 runtime.addPlugin(
   new AzureBlobPlugin<AzureBlobLogEntry>({
-    sasUrl: "https://YOUR_ACCOUNT.blob.core.windows.net/YOUR_CONTAINER?sv=2022-11-02&ss=b&srt=co&sp=wactfx&se=2045-11-17T13:50:53Z&st=2024-11-17T05:50:53Z&spr=https&sig=YOUR_SIG",
+    sasUrl:
+      "https://YOUR_ACCOUNT.blob.core.windows.net/YOUR_CONTAINER?sv=2022-11-02&ss=b&srt=co&sp=wactfx&se=2045-11-17T13:50:53Z&st=2024-11-17T05:50:53Z&spr=https&sig=YOUR_SIG",
     batchPeriodSeconds: 1,
     generateLogEntry,
-  })
+  }),
 );
-
 ```
 
 The plugin writes Block Blobs using SAS signatures. Ensure that your SAS URL has

docs/articles/rick-and-morty-api-developer-portal-example.md

@@ -9,7 +9,8 @@ gateway configuration. for the Rick and Morty API.
 The Rick and Morty API is a REST(ish) API based on the television show Rick and
 Morty. It provides access to hundreds of characters, images, locations and
 episodes. The Rick and Morty API is filled with canonical information as seen on
-the TV show. Full credit to the original and upstream API, which is available at rickandmortyapi.com.
+the TV show. Full credit to the original and upstream API, which is available at
+rickandmortyapi.com.
 
 > "I'm A Scientist; Because I Invent, Transform, Create, And Destroy For A
 > Living, And When I Don't Like Something About The World, I Change It."