Initial state: - ia_dev was historically referenced as ./ia_dev in docs and integrations, while the vendored module lives under services/ia_dev. - AnythingLLM sync and hook installation had error masking / weak exit signaling. - Proxy layers did not validate proxy path segments, allowing path normalization tricks. Motivation: - Make the IDE-oriented workflow usable (sync -> act -> deploy/preview) with explicit errors. - Reduce security footguns in proxying and script automation. Resolution: - Standardize IA_DEV_ROOT usage and documentation to services/ia_dev. - Add SSH remote data mirroring + optional AnythingLLM ingestion. - Extend AnythingLLM pull sync to support upload-all/prefix and fail on upload errors. - Harden smart-ide-sso-gateway and smart-ide-global-api proxying with safe-path checks and non-leaking error responses. - Improve ia-dev-gateway runner validation and reduce sensitive path leakage. - Add site scaffold tool (Vite/React) with OIDC + chat via sso-gateway -> orchestrator. Root cause: - Historical layout changes (submodule -> vendored tree) and missing central contracts for path resolution. - Missing validation for proxy path traversal patterns. - Overuse of silent fallbacks (|| true, exit 0 on partial failures) in automation scripts. Impacted features: - Project sync: git pull + AnythingLLM sync + remote data mirror ingestion. - Site frontends: SSO gateway proxy and orchestrator intents (rag.query, chat.local). - Agent execution: ia-dev-gateway script runner and SSE output. Code modified: - scripts/remote-data-ssh-sync.sh - scripts/anythingllm-pull-sync/sync.mjs - scripts/install-anythingllm-post-merge-hook.sh - cron/git-pull-project-clones.sh - services/smart-ide-sso-gateway/src/server.ts - services/smart-ide-global-api/src/server.ts - services/smart-ide-orchestrator/src/server.ts - services/ia-dev-gateway/src/server.ts - services/ia_dev/tools/site-generate.sh Documentation modified: - docs/** (architecture, API docs, ia_dev module + integration, scripts) Configurations modified: - config/services.local.env.example - services/*/.env.example Files in deploy modified: - services/ia_dev/deploy/* Files in logs impacted: - logs/ia_dev.log (runtime only) - .logs/* (runtime only) Databases and other sources modified: - None Off-project modifications: - None Files in .smartIde modified: - .smartIde/agents/*.md - services/ia_dev/.smartIde/** Files in .secrets modified: - None New patch version in VERSION: - 0.0.5 CHANGELOG.md updated: - yes
45 lines
1.1 KiB
Markdown
45 lines
1.1 KiB
Markdown
# Lapce patches (Smart IDE)
|
|
|
|
This folder versions the **Smart IDE** modifications applied to **Lapce**.
|
|
|
|
Why this exists:
|
|
|
|
- The Lapce checkout lives in `core_ide/` (and is ignored by the parent `smart_ide` git repository).
|
|
- We still want a **reviewable**, **replayable** history of the core editor changes.
|
|
|
|
## Files
|
|
|
|
- `series`: ordered list of patch filenames to apply (one per line, `#` comments allowed).
|
|
- `*.patch`: `git format-patch` output generated from `core_ide/`.
|
|
|
|
## Workflow
|
|
|
|
### Apply patches to `core_ide/`
|
|
|
|
From the `smart_ide` repo root:
|
|
|
|
```bash
|
|
./scripts/core-ide-apply-patches.sh
|
|
```
|
|
|
|
### Export patches from `core_ide/`
|
|
|
|
1. Make commits inside `core_ide/` (in a dedicated branch, e.g. `smart-ide`).
|
|
2. Export the patch series:
|
|
|
|
```bash
|
|
./scripts/core-ide-export-patches.sh
|
|
```
|
|
|
|
This regenerates `patches/lapce/*.patch` and rewrites `patches/lapce/series`.
|
|
|
|
## Remotes
|
|
|
|
Recommended convention inside `core_ide/`:
|
|
|
|
- `upstream`: official Lapce (`https://github.com/lapce/lapce.git`)
|
|
- `origin`: internal fork (team forge)
|
|
|
|
Use `./scripts/ensure-core-ide.sh --fork-url <...>` to set this up.
|
|
|