Files
Jack 751208659d chore: keep generated images inside the project as real directories
The absolute-path + symlink layout added earlier today is awkward to
redeploy against: after a fresh clone the symlinks point at nothing and
compose quietly creates empty directories in their place, so the service
comes up healthy with no history.

/root/apps/ holds services only, so the images and the SQLite database
live in the project again as ./output and ./data, bind-mounted with
relative paths. Backups are handled by a separate hook that copies to
/root/backup_files/ai-image/, which is not part of /root/apps/.

Both directories stay gitignored.
2026-11-04 23:57:55 +08:00

50 lines
653 B
Plaintext

# Environment and secrets
.env
.env.*
!.env.example
# Local runtime data (SQLite + 加密密钥) 与生成图片
# 这两个是本服务的真身目录,不进 git。
# 备份由 ruantang profile 的 backup-ai-image-output.sh 负责,
# 落到 /root/backup_files/ai-image/。
data/
output/
.screenshots/
.trae-html-share-packages/
# Test scratch
test/
# Python
__pycache__/
*.py[cod]
*$py.class
*.so
.Python
.pytest_cache/
.mypy_cache/
.ruff_cache/
.coverage
htmlcov/
# Virtual environments
.venv/
venv/
env/
# Packaging
build/
dist/
*.egg-info/
# IDE and OS
.vscode/
.idea/
*.iml
.DS_Store
Thumbs.db
# Logs and local databases
*.log
*.sqlite3