From f0225fb59d0d647cfdca350fb214652622286680 Mon Sep 17 00:00:00 2001 From: pi Date: Tue, 25 Aug 2026 04:11:13 +1200 Subject: [PATCH] docs: fix grammar issue in deployment.md (missing_comma_without_it) --- docs/deployment.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/deployment.md b/docs/deployment.md index 09e4ec35..3972f827 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -33,7 +33,7 @@ enable it for you. **Not in it:** **The supervisor.** It gives each Bot its own container, which needs a Docker socket, which no -serverless container platform permits. Without it every Bot shares the one browser, exactly as they +serverless container platform permits. Without it, every Bot shares the one browser, exactly as they do on a laptop with no supervisor configured. A shared browser means shared logins, shared files and shared session between Bots, which is fine for a deployment where one team trusts its own Bots and is not fine as a boundary between tenants. @@ -86,7 +86,7 @@ deployment. `NODE_ENV` does not affect this. **Put TLS in front of it.** Not only for the cookies. A page served from `http://
` is not a secure context, which removes a set of browser APIs that are present on `http://localhost` and so -never missing on a laptop. The app no longer depends on any of them, but sign-in cookies still want +never missing on a laptop. The app does not depend on any of them, but sign-in cookies still want `Secure`, and every platform below terminates TLS for you. ## Migrations @@ -123,7 +123,7 @@ in ECR, and is what AWS points App Runner users at now that App Runner takes no Plain ECS on Fargate behind an ALB is the answer if you want task definitions and fine-grained IAM. No shared-memory configuration is needed or possible. -**Azure Container Apps.** Managed ingress with TLS and custom domains. Note the **240 second request +**Azure Container Apps.** Managed ingress with TLS and custom domains. Note the **240-second request timeout**: the live screen holds a long connection, so expect it to reconnect. Concurrent WebSockets are capped at 350 per instance on the basic tier.