feat(env): add environment variable management script and update database copy command

- Introduced a new script `mv-env.sh` to manage environment variable files, copying `.env.prod` if it exists, otherwise falling back to `.env.example`.
- Updated the `cp:db` command in `package.json` to utilize the new script for improved environment configuration handling.

These changes enhance the project's environment setup process, ensuring the correct environment variables are used during deployment.

package.json

@@ -10,7 +10,7 @@
     "build": "bun run sync:vditor && nuxt build && bun run cp:db && bun --elide-lines=0 --filter drizzle-pkg build",
     "dev": "bun run sync:vditor && nuxt dev",
     "sync:vditor": "sh scripts/sync-vditor-assets.sh",
-    "cp:db": "cp build-files/run.sh .output/run.sh && cp .env.example .output/.env && cp -r build-files/migrate/* .output/server/ && cp build-files/seed.js .output/server/seed.js",
+    "cp:db": "cp build-files/run.sh .output/run.sh && sh scripts/mv-env.sh && cp -r build-files/migrate/* .output/server/ && cp build-files/seed.js .output/server/seed.js",
     "migrate:test": "sh scripts/migrate-test.sh",
     "db:migrate": "bun --elide-lines=0 --filter drizzle-pkg migrate",
     "db:generate": "bun --elide-lines=0 --filter drizzle-pkg generate",

scripts/mv-env.sh

@@ -0,0 +1,5 @@
+if [ -f .env.prod ]; then
+  cp .env.prod .output/.env
+else
+  cp .env.example .output/.env
+fi