chore: clean up proxy config and remove unused test script

[larryro]

• Remove ACME_EMAIL from README example (no longer needed)
• Delete unused services/db/test-setup.sh test script
• Remove debug-level global config block from Caddyfile
• Change Caddyfile log level from DEBUG to INFO

Summary by CodeRabbit

• Chores
  • Removed default environment variable from configuration documentation
  • Reduced logging verbosity by adjusting log level settings
  • Removed database test setup script from repository

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Three files were modified to remove or simplify configuration and testing infrastructure. The README.md had an environment variable line removed from deployment instructions. The entire services/db/test-setup.sh file, which contained a 12-step end-to-end test workflow for a Tale DB Docker container setup, was deleted. The services/proxy/Caddyfile was updated to remove the global configuration block with debug and email settings and to change the log level from DEBUG to INFO.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify that the database testing functionality provided by test-setup.sh has been relocated to another test suite or framework
• Confirm that changing the proxy log level from DEBUG to INFO does not suppress critical operational logs needed for monitoring or troubleshooting
• Check if the ACME_EMAIL removal from README.md is intentional or if it should be documented elsewhere in the deployment guide

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between d1dbc84 and e439319.

📒 Files selected for processing (3)

• README.md (0 hunks)
• services/db/test-setup.sh (0 hunks)
• services/proxy/Caddyfile (1 hunks)

💤 Files with no reviewable changes (2)

• README.md
• services/db/test-setup.sh

🧰 Additional context used

📓 Path-based instructions (1)

**/*

📄 CodeRabbit inference engine (.cursor/rules/workspace_rules.mdc)

Use English only for ALL user-facing content including UI components, labels, buttons, dialogs, forms, toast messages, error messages, success messages, comments, documentation, README files, variable names, function names, and type names

Files:

• services/proxy/Caddyfile

🔇 Additional comments (2)

services/proxy/Caddyfile (2)

24-24: LGTM! Appropriate log level for production.

Changing from DEBUG to INFO reduces log verbosity and is the standard choice for production environments.

---

14-19: Verify removal of ACME email configuration is intentional.

The PR removed the ACME email configuration (both from the global config and the README example). While Caddy's automatic certificate renewal will continue to function, ACME providers like Let's Encrypt and ZeroSSL use email addresses to send important notifications about certificate expiration, renewal failures, or account issues.

Please confirm:

1. Is the removal of ACME email intentional?
2. Are certificate expiration notifications being monitored through alternative means?

If notifications are desired, consider adding the email back to the ACME issuer configuration:

 tls {
   issuer acme {
     dir {$ACME_CA:https://acme-v02.api.letsencrypt.org/directory}
+    email {$ACME_EMAIL}
     disable_tlsalpn_challenge
   }
 }

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}