Default domain
🌍
Works on first deploy.
Each environment has a unique default domain, a subdomain of frbit.app, that works right after creation without any DNS configuration. It was called test domain before.
Structure
Default domains follow a predictable naming pattern: {environment}.{region}.frbit.app, where environment is the unique app environment identifier, region indicates the data center location, and frbit.app is the fortrabbit root domain.
{{ environment }}.{{ region }}.frbit.app
environment — ID, short unique identifier
region — data center region ID, geo location
frbit.app — fortrabbit associated root domain
raw
- Example:
https://en-34fdsa.eu-w1a.frbit.app - Live code example:
{{app-env-id}}.{{region}}.frbit.app(login required) - TLS is included. The default domain is always served over HTTPS.
Use cases
- Test — open the environment in a browser after deploy without any setup.
- Share work in progress — send the default domain to a colleague or client.
- Staging environments — use the default domain for feature development preview.
- CI/CD pipelines — reference the default domain in automated tests or health checks.
Limits
- The name can not be changed. The environment ID part of the default domain is fixed at environment creation time.
- The default domain can not be deleted.
- The default domain is not a replacement for a production domain. For a customer-facing address, add an external domain.