Repository navigation
Security notice: deploy --remote-build
Before this release, togo deploy --remote-build uploaded the whole project directory, including .env, .git and local database files. It now excludes .env, .env.* (except .env.example), .git/, *.db / *.sqlite files (and -wal/-shm), node_modules/ and .togo/, honours .gitignore, and requires rsync (no scp fallback). Use deploy.include to ship an excluded path on purpose.
Action required if you used --remote-build before: remove stale .env, .git and database files from the server's deploy path, and rotate any secrets that were in that .env (AUTH_SECRET, database credentials, API keys).
Other changes
togo newtreats redirected stdin (/dev/null,NUL) as non-interactive and no longer startsdocker composeon its own (#4).- Repo enforces LF line endings (
.gitattributes) and CI checks the packed npm tarball for CR bytes (#9).
Changelog
- 7e48d50: fix(deploy): never upload .env, .git or local databases with --remote-build (#20) (@fadymondy)
- dc7f522: fix(new): treat redirected stdin as non-interactive (#18) (@fadymondy)
- b2becf7: fix(npm): enforce LF line endings and guard the packed tarball (#19) (@fadymondy)
- 32d4476: release: v0.2.37 (@fadymondy)