tauri-dotenv-working-directory

Tauri environment variables return not set errors because dotenvy uses incorrect relative paths during development. Since cargo tauri dev runs with the working directory at the project root, paths like ../../.env fail to locate the file, requiring a multi-path loading approach.

To load environment variables in a Tauri app, add a multi-path env loader to your entry point and verify critical variables at startup. Run cargo tauri dev from the project root so API keys and config like GHOST_URL are available without missing env vars errors.

Cargo tauri dev runs with the current working directory at the project root, not at ui/src-tauri. This working directory context means relative paths like ../../.env fail to resolve, so .env files must be loaded directly from the root context.

The best way to verify API keys in Tauri development is to implement explicit environment-variable verification at startup. This prevents silent failures when GhostClient::from_env() or similar functions try to read missing config variables from incorrectly loaded .env files.

Yes, you can use a multi-path loading approach to fix missing config in Tauri commands. By checking multiple potential file locations and verifying critical environment variables at startup, you prevent silent failures when API keys work locally but not in the Tauri app.