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
{{ message }}
Repository navigation
Commit dba6053
Browse filesBrowse the repository at this point in the historyBrowse files
fix(security): re-scope to owned release-audit items on current staging
Drops the response cap and crawl depth (landed in #9860), CONTRIBUTING (#9860), Firecrawl search sources (on hold), Databricks JSON caps (#9859), and the workflow middleware and route-policies cleanups (#9858). Drops the NO_PROXY entry-syntax docs line (owned by a separate NO_PROXY change). Generated files regenerated on current staging.
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,22 +140,20 @@ Using clear and consistent commit messages makes it easier for everyone to under
140
140
141
141
To set up your local development environment:
142
142
143
-
### Option 1: Using the setup wizard (Simplest)
143
+
### Option 1: Using the Setup Wizard (Simplest)
144
144
145
-
The easiest way to run Sim locally is the `sim-setup` wizard:
145
+
The easiest way to run Sim locally is the interactive setup wizard:
146
146
147
147
```bash
148
148
npx sim-setup
149
149
```
150
150
151
-
The wizard checks Docker, ports, memory, and disk space, generates the required secrets, writes `.env` and a Docker Compose file into a new `sim` directory, starts the containers, runs database migrations, and waits for the health checks to pass. When it finishes, open [http://localhost:3000/](http://localhost:3000/) in your browser.
151
+
When it finishes, open [http://localhost:3000/](http://localhost:3000/) in your browser. Inside a cloned Sim repository, run `bun run sim-setup --mode dev` for the local development mode.
152
152
153
153
#### Requirements
154
154
155
-
- Node.js 20 or newer
156
-
- Docker with the Compose plugin, installed and running
157
-
158
-
See the [`sim-setup` README](../packages/sim-setup/README.md) for options and management commands.
155
+
- Node.js 20+
156
+
- Docker must be installed and running on your machine
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/firecrawl.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,7 +184,7 @@ Crawl entire websites and extract structured content from all accessible pages
184
184
| --------- | ---- | -------- | ----------- |
185
185
|`url`| string | Yes | The website URL to crawl \(e.g., "https://example.com" or "https://docs.example.com/guide")|
186
186
|`limit`| number | No | Maximum number of pages to crawl \(e.g., 50, 100, 500\). Default: 100 |
187
-
|`maxDepth`| number | No | Maximum path depth below the starting URL \(e.g., 1 from /docsallows /docs/guide and /docs/guide/index.html\). Independent of link discovery depth |
187
+
|`maxDepth`| number | No | Maximum URL path depth below the starting URL \(e.g., from /docs, 1 allows /docs/guide\). Independent of link discovery depth |
188
188
|`formats`| json | No | Output formats for scraped content \(e.g., \["markdown"\], \["markdown", "html"\], \["markdown", "links"\]\)|
189
189
|`prompt`| string | No | Natural-language crawl guidance supplied by existing configurations |
190
190
|`excludePaths`| json | No | URL paths to exclude from crawling \(e.g., \["/blog/*", "/admin/*", "/*.pdf"\]\)|
Copy file name to clipboardExpand all lines: apps/docs/content/docs/platform/self-hosting/networking.mdx
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -301,8 +301,6 @@ A request through the SSRF guard keeps its checks when it is proxied. Before eac
301
301
302
302
Set `NO_PROXY` for every destination that is not on the public internet, not just model endpoints. The app reaches the realtime server (`SOCKET_SERVER_URL`), the Presidio PII service (`PII_URL`), and itself (`INTERNAL_API_BASE_URL`) over the same default `fetch`, alongside self-hosted Ollama, LiteLLM, and vLLM — so a proxy that cannot reach your internal network breaks live updates and PII redaction, not only inference. AWS clients and OTLP export follow the same rule, so also add an internal S3-compatible store such as MinIO, AWS VPC endpoints, and an in-cluster OpenTelemetry collector.
303
303
304
-
Each entry is a hostname, a domain suffix (`.svc` or `*.svc`), or an IP address, optionally followed by `:port`. Bracket IPv6 addresses (`[::1]`). CIDR ranges are not supported. `*` disables the proxy only when it is the whole value.
305
-
306
304
Set it in the application environment, not your shell — under `app.env` on Helm, or the service's `environment:` on Compose. On Helm the suffixes alone are not enough: the chart wires `SOCKET_SERVER_URL`, `PII_URL`, and `OLLAMA_URL` to bare Service names, which no domain suffix matches. Add those names too — `helm template` prints the rendered ones, and the prefix is the release name unless it already contains `sim`, in which case it is the release name alone:
0 commit comments