tauri-react-nest-lan-migration

Tauri React + Nest LAN Migration

Apply this flow in order to minimize risks in Web -> Desktop migrations.

Recommended flow

1. Plan migration
2. Implement changes in backend/frontend/tauri
3. Verify setup, login and CRUD with logs
4. Prepare installable release

Mandatory LAN rules

• Desktop backend always local: 127.0.0.1
• Remote database: fixed server IP in database.host
• Do not use localhost as DB host on LAN clients

Logs to check first

• %APPDATA%/sistema-caja/debug_startup.log
• %APPDATA%/sistema-caja/logs/error-YYYY-MM-DD.log
• %APPDATA%/sistema-caja/logs/application-YYYY-MM-DD.log

Quick diagnosis of frequent errors

• Cannot POST /api/config/test

  • Backend in normal mode and not in setup

• failed to fetch

  • Backend down or restarting (startup race)

• Unexpected token when parsing config

  • File with BOM (e.g. config.json)

• os error 2

  • Sidecar path or name poorly resolved

• os error 32

  • Files locked during extraction/use

• Nest can't resolve JwtAuthGuard (JwtService)

  • Auth module not imported/exported where it belongs

Minimum verification checklist

• Initial setup opens and saves configuration
• Login works with sidecar backend
• Critical CRUD works with remote DB by IP
• There are no blocking errors in startup logs

Go/No-Go criteria

• Go: setup + login + CRUD + stable logs
• No-Go: sidecar errors, backend crashes, or auth/DB failures