Clarify .env files

[dawsontoth]

I shuffled several of the .env files used for deployments to be hidden in a sub-directory, and then I clarified on fabric vs local mode. I removed a few confusing package.json scripts by passing more flags in the GitHub actions too. All in all, it should be less confusing now, I hope. The .env.local becomes your single local environment file, nothing else is needed.

Aside from local verification and careful perusal of the changes, I also pushed this to dev successfully https://github.com/HarperFast/studio/actions/runs/27431497498

https://harperdb.atlassian.net/browse/STUDIO-361

[gemini-code-assist]

Code Review

This pull request reorganizes the environment configuration by moving build-mode env files to .github/deploy-public-env and dynamically setting Vite's envDir based on the active mode. It also refactors the development and build scripts in package.json, the Makefile, and documentation to support this structure. Feedback highlights that setting envDir redirects Vite's search for .env.local to that directory, which should be documented in the configuration comments. Additionally, the inline environment variable definition in the dev:local script is not cross-platform and should use cross-env to support Windows environments.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[cb1kenobi]

Awesome!