# dvx.conf carries the console token and the relay password, and review.conf the token and the
# path to the repository's secret key:  both are per-deployment.  dvx.conf.example belongs in history.
dvx.conf
review.conf
data/
review/
*.log

# The tests' keys, packages, and database, made fresh on every run
test/data/

# Secret keys never belong in history;  the repository's stays on the operator's own computer.
*.SEC

# The top-level lib/ rule is for the build's libraries;  this lib/ is the server's own source.
!lib/