Smoother self-hosting for Docker & Railway

We've made self-hosting Quackback easier, especially if you're running Docker or deploying to Railway.

Email is now optional

You no longer need an email provider configured to get started. If SMTP or Resend isn't set up, Quackback automatically adapts:

• The email sign-in option is hidden from the login page
• Invitation flows return the invite link directly so you can share it manually
• Everything else works normally

This makes it much faster to spin up a local instance for evaluation or internal use.

S3 proxy mode

A new S3_PROXY option streams file uploads through the server instead of redirecting to your storage endpoint.

This fixes broken avatars and images in common self-hosting scenarios:

• ngrok tunnels where the browser can't reach S3 directly
• Docker networking with internal-only MinIO
• Mixed HTTP/HTTPS setups behind a reverse proxy

More resilient configuration

Empty environment variables in Docker Compose no longer cause startup failures for optional fields — a common pain point when working from example configs.

Bug fixes

• Fixed a deployment-blocking issue where a missing migration caused errors on every request
• Fixed image serving for private S3 buckets (e.g. Railway Buckets)
• Fixed test configuration picking up e2e specs incorrectly