Naming Conventions for tb.pro

Backend

For our TB services, we follow this convention for the backend:

[product]-backend[-env].tb.pro

where -env is either -stage or -dev, or empty if it's production.

Example: send-backend-stage.tb.pro for staging, and send-backend.tb.pro for production

Follow this convention:

[product][-env].tb.pro

where [-env] is either dev for dev, stage for staging, or ignored for prod

Example: send-stage.tb.pro for staging, and send.tb.pro for production