4nk/smart_ide
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
35 Commits 1 Branch 0 Tags
Commit Graph

3 Commits

Author SHA1 Message Date
Nicolas Cantu
1265be0d11 Align enso remote paths with enso-deploy conventions 
**Motivations:**
- Project conf remote_data_access should match deploy script variables (absolute paths on target hosts).

**Correctifs:**
- Replace /var/lib/enso/... placeholders with ENSO_REMOTE_ROOT and default docv dossiers-permanents path.
- Use ssh_host_alias values aligned with ENSO_SSH_HOST per env in enso-deploy.env.example.

**Evolutions:**
- Document optional remote_app_root and script references in remote-deployed-data-ssh.md and projects/README.md.
 2026-04-03 18:06:37 +02:00
Nicolas Cantu
4d04eed0f3 feat: relative paths in projects/conf.json and cron pull resolution 
- project_path, deploy.*, cron: resolve from monorepo root; ia_dev submodule bumped
- enso/smart_ide.code-workspace folder paths ../../enso, ../../builazoo
- Document in projects/README, remote-deployed-data-ssh.md
 2026-04-03 18:03:59 +02:00
Nicolas Cantu
0f9a69e368 docs: deployed data over SSH, docv/AnythingLLM/services, IDE project config 
- Add features/remote-deployed-data-ssh.md (source of truth on test/pprod/prod)
- Extend projects conf smart_ide.remote_data_access and anythingllm slugs (enso example)
- active-project.json.example + gitignore; .vscode/settings smartIde.activeProjectId
- Update docv integration docs, anythingllm-workspaces, ecosystem, API README
- Cursor rule: resolve project id from active-project / env / workspace setting
 2026-04-03 17:55:08 +02:00