Environments
The Cabman Cloud Platform has a few different environments. CCP is developed with the following lifecycle and results in two distinct internal and two distinct external environments.
Development
After conceptualy creating a new feature it's developed by one of our developers. Every internal Euphoria developer has a local instance of CCP available to develop the feature on. When the feature is complete and has gone through a review the feature is deployed on our internal testing server.
Testing
At this point the developers of the client software (Cabman Centrale, the android and iOS apps) use this environment to update their software to the new features. It is also where our Q&A team tests the new features. When they sign off on the changes it is deployed to an external staging environment.
Staging
The staging environment is where 3rd party developers can develop or update their software to the new feature set. The staging environment is also used to showcase new features to clients.
The staging environment has the following public endpoint
OData service: https://staging.cabmanonline.nl/CCPService/DataServiceCCP.svc
After a usually short testing period and after an okay from all stakeholders the staging environment is copied to the live environment.
Live
The live environment is the main endpoint for customers and their clients. It is also the environment where all published applications connect to.
The live environment has the following public endpoint
OData service: https://www.cabmanonline.nl/CCPService/DataServiceCCP.svc