Use a hex Postgres password in the production example

A base64 password can contain / and =, which break the DATABASE_URL.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MzFywujuH9TiuXbr9vjoX8

deploy/production.env.example

@@ -2,8 +2,9 @@
 
 DOMAIN=musicshare.binarygnome.com
 
-# Generate each with: openssl rand -base64 32
+# openssl rand -hex 32   (hex: the password goes inside a URL, so no / + = characters)
 POSTGRES_PASSWORD=
+# openssl rand -base64 32   (reuse the old key when importing a database, or saved connections break)
 TOKEN_ENCRYPTION_KEY=
 
 # Optional: exact "Open in Spotify" links (catalog search only; no user sign-in)