# SHiNE configuration EXAMPLE. This file is never loaded automatically. # Copy it to application.properties in the server working directory, # or provide a private application.properties on the server classpath. # Never commit application.properties with real credentials. # Database: replace with your own test/server values. db.url=jdbc:postgresql://localhost:5432/shine db.user= db.password= server.SHiNE.login= # Solana/Arweave: disabled until configured. solana.cluster=devnet solana.rpcUrl= solana.users.sync.enabled=false blockchain.sync.enabled=false sync.importUserProfileFromPartner.enabled=false arweave.blocks.publish.enabled=false arweave.blocks.sync.enabled=false # Temporary / testing endpoints: off by default. debug.tempApi.enabled=false test.freeAvatar.enabled=false # Other services: fill in real values only in the private config. dm.delivery.enabled=false webpush.vapid.public= webpush.vapid.private= webpush.vapid.subject= call.ice.turn.sharedSecret= # Email verification for free registration: requires the separate allowlist file. # The deployment script copies allowed-email-domains.txt alongside shine-server.jar. freeRegistration.email.allowedDomainsFile=allowed-email-domains.txt # R2 public attachment direct uploads (keep credentials in server environment) r2.publicBucket=shine-files # R2_ENDPOINT=https://.r2.cloudflarestorage.com # R2_ACCESS_KEY_ID=... # R2_SECRET_ACCESS_KEY=... # R2 DM encrypted attachments (publicly downloadable ciphertext, 14-day lifecycle) r2.dmBucket=shine-dm # Configure R2 credentials via R2_ENDPOINT, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY