# DigiDala Alpha 50.9.13 — production infrastructure candidate

**Status:** local production-infrastructure candidate; not committed, tagged or deployed.

## Scope

This candidate adds the first version-controlled production runtime for DigiDala while preserving the existing staging environment unchanged.

### Production identity

```text
Public product: DigiDala
Domain:         https://digidala.ru/
Bot:            @DigiDala_bot
Root:           /opt/digidala
Web:            127.0.0.1:8082
API:            127.0.0.1:8091
Database:       /opt/digidala/data/digidala-production.db
```

### Added production infrastructure

- `digidala-production-web.service`
- `digidala-production-api.service`
- `digidala-production-bot.service`
- HTTP bootstrap and HTTPS Nginx configurations for `digidala.ru`
- `scripts/deploy-production.sh`
- `scripts/rollback-production.sh`
- `.env.production.example`
- production deployment documentation and regression tests

### Isolation

Production has its own runtime directory, database, campaign assets, ports, environment file and systemd service names.
The existing staging environment remains:

```text
im-test.bktis.ru
@PixDala_bot
/opt/pixdala
```

### Scope boundary

This candidate does not switch DNS, does not create the production database on the VPS, does not issue a certificate, and does not start `@DigiDala_bot`.
Those are controlled one-time infrastructure steps after the candidate passes staging checks.