Although Servitly offers a console where you can configure your DPS with a codeless approach, developing your solution directly in the production environment is not a good idea.
As done for standard web applications that must be tested first and then deployed, a best practice is to leverage the DEVELOP and STAGING environments.
You can start your configuration activities in the DEVELOP environment, and when you are ready to go into production, you should move the configuration to STAGING, verify that everything is OK, and finally promote it to PRODUCTION.
To help you with this task, you can use the Compare and Import tool that is available in the console within the environment you want to update.
For example, here are the steps to follow to add a new Thing Definition.
In your Project view, open the DEVELOP environment
Configure the new Thing Definition (metrics, events, templates, etc.)
Test your configuration by using a Virtual Thing and User Views.
For more details, you can refer to the Initial DPS Configuration article.If your configuration is complete, you can now promote the new thing definition to the STAGING environment, where it can be validated (e.g., peer review).
In your Project view, open the STAGING environment.
Enter the Overview page, select Configuration Management, and click the Compare Configuration button.
Select the STAGING environment as the source environment to compare.
Select the changes you want to import, in this case, the newly created thing definition.
Update the STAGING environment by importing all the selected changes.
Test your STAGING configuration by using a Virtual Thing and User Views.
If the STAGING configuration is valid, you can now move to production by using the Compare and Import tool between STAGING (source) and PRODUCTION (target) environments.
In this case, the comparison will be easier because everything that is present in STAGING will be imported into PRODUCTION.