1.2 - Project Environments

Dev, Test and Prod:

When developing software projects, it makes sense to have a number of different environments that will allow you to develop without it affecting testing or production systems.

In most cases, these will be a Dev, Test/UAT, and Production environment.

For CMS based answerSpace environments, these are usually named using a -[environment] at the end of your project name.

CMS based example:

• blinkm.co/myproject-dev
• blinkm.co/myproject-test
• blinkm.co/myproject-prod

For a file-based development approach, when you deploy your code into our Web Client Hosting service, you will be using a structure similar to:

File-based example:

• company-project-dev.blinkm.io
• company-project-test.blinkm.io
• company-project.blinkm.io

All You Can Eat:

The Blink Mobility Platform comes as an all-you-can-eat service - this means your development environments don't cost any extra, and if you need a fourth environment (perhaps for training), then just ask! Multiple develoment environments help you to keep your project clean, easy to maintain, offer the ability for development efforts to never interfere with stable production or even user testing environments.

Next:

1.3 - Development Lifecycle for CMS Based Development