Transity Deployment and Operations
Transity supports local container-based development and an automated production delivery path. The current deployable artifact is the backend service.
Local deployment
Docker Compose
From the Transity repository root:
Service | Address | Notes |
|---|---|---|
Backend |
| Application API and company UI |
The backend uses the Swiss company database by default. Select another supported country with M8TY_COUNTRY; each country has an isolated database with the same public data model.
Production deployment
The current production path deploys the backend only.
The delivery pipeline derives a release version from Git tags.
Automated tests validate the backend.
A production container image is built and published with release and commit identifiers.
The deployment is upgraded in the target environment.
The service is published at
https://transity.m8ty.euusing Transport Layer Security (TLS).
The production image runs as an unprivileged user and includes the Swiss company database. Company synchronization and logo acquisition run outside the request-serving workload. Verified logos are served through the configured content delivery network (CDN).
Runtime configuration
Application settings use the M8TY_ prefix.
Variable | Default or deployed value | Purpose |
|---|---|---|
|
| Select the country database |
|
| Application log level |
| Deployment-specific | Public base URL for verified logos |
|
| Enable request limiting |
| Deployment-specific | Read the client IP supplied by the trusted edge proxy |
Operational checks
After deployment, verify the public service:
The first two commands must return an HTTP success response. The search request additionally proves that the deployed application can open and query its bundled company database.
See Also
Transity — product overview and topic index
Product and Architecture — data sources and system design
Transity API — endpoints and examples