Adshares AdServer configuration should be treated as a revenue-impacting control plane.
Focus areas are wallet/security settings, delivery integrity, and predictable reporting.
Most self-hosted deployments use env-driven configuration in the application stack.
Example baseline:
APP_ENV=production
APP_URL=https://adshares.example.com
DB_HOST=127.0.0.1
DB_PORT=5432
DB_NAME=adshares
DB_USER=adshares
DB_PASSWORD=replace-with-long-random-secret
REDIS_URL=redis://127.0.0.1:6379/0
TZ=UTC
LOG_LEVEL=info
¶ Campaign and placement controls
- Enforce strict approval workflow before a campaign can go live.
- Define per-zone limits (formats, dimensions, max frequency).
- Separate test inventory from production inventory.
- Track invalid traffic and rejected clicks as first-class metrics.
- Keep admin/API endpoints behind TLS and optional VPN.
- Store signing/wallet credentials in secret store, not in plain env files.
- Rotate DB and API credentials on a scheduled cycle.
- Audit administrator actions and export logs to a central system.
¶ Reporting and retention
- Set a clear raw-event retention window based on storage budget.
- Keep aggregated reporting data longer than raw click events.
- Export monthly campaign/billing snapshots to immutable storage.
- Backup PostgreSQL and Redis persistence.
- Backup environment files and deployment manifests (without exposing secrets).
- Test point-in-time restore before major upgrades.
- Validate one historical campaign report after restore.
- API health endpoint monitored.
- Queue latency and failed delivery counts alerting enabled.
- DB disk growth and write latency monitored.
- Rollback procedure documented for failed release.
Running Adshares Adserver in regulated environments? We assist with:
- 🔐 TLS/SSL configuration
- 🔑 Authentication and authorization setup
- 📋 Audit logging and compliance reporting
- 🛡️ Security hardening benchmarks (CIS, STIG)
Secure your deployment: office@linux-server-admin.com | Contact Page