openvisengine/.gitignore
zai-bot 6dd7f7ead7 Merge origin/zai-dev — integrate operator's tracked .env/.env.ove (3286721)
The operator hand-pushed .env and .env.ove tracked while this task ran,
both with DATABASE_URL="file:./db/custom.db" — the relative form that
Prisma resolves against prisma/schema.prisma's directory, i.e. to
<repo>/prisma/db/custom.db, breaking the CLI (db push would silently
create a fresh empty database there) and the runtime (cannot open);
verified empirically. The merge keeps .env tracked per the operator's
explicit action (gitignore: !.env) and corrects DATABASE_URL in both
files to the portable file:../db/custom.db. The committed .env is held
byte-identical to .env.ove so dev.sh's self-heal copy never leaves a
dirty tree.
2026-11-06 08:02:42 +00:00

78 lines
1.4 KiB
Text
Executable file

# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
# dependencies
node_modules
/.pnp
.pnp.*
.yarn/*
!.yarn/patches
!.yarn/plugins
!.yarn/releases
!.yarn/versions
# testing
/coverage
# next.js
/.next/
/out/
# production
/build
/dist
# misc
.DS_Store
*.pem
# debug
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*
# env files (can opt-in for committing if needed)
.env*
!.env.example
# .env + .env.ove — TRACKED by operator authorization (strictly private
# self-hosted Forgejo only); dev.sh restores .env from the template after
# sandbox reprovisions, and the committed .env stays byte-identical to it
!.env
!.env.ove
# databases -- runtime state, regenerated per machine (prisma db push);
# the committed baseline snapshot is the self-healing seed (Task 47)
*.db*
*.sqlite
*.sqlite3
!db/custom.db.seed
# vercel
.vercel
# typescript
*.tsbuildinfo
next-env.d.ts
local-*
.claude
.z-ai-config
# runtime logs & local scratch (dev server output, platform pid)
*.log
dev.log
dev.out.log
test
prompt
server.log
.zscripts/dev.pid
# Skills directory
/skills/
# z.ai session artifacts (tool output dumps / e2e screenshots) -- not project content
/tool-results/
# secrets/ IS tracked (operator-authorized: strictly private self-hosted
# Forgejo repo — the house-account cookies ride with the repo so sandbox
# reprovisions can never wipe them). See secrets/README.md.