How can I manage the dev and live environments with Batch?
Here are the best practices to manage both environments.
A staging environment refers to a parallel server environment for testing websites and software applications in conditions as close as possible to the live environment, without compromising the organization's current data or interrupting its operations.
You should always integrate Batch in a development environment and then go into production mode after everything has been tested and validated.
For this matter, we strongly recommend:
1
Creating two applications per OS (Android, iOS, Web) on the dashboard: one for tests and one for production (e.g. MyApp and [DEV] MyApp).
2
These apps will then be grouped into two Omnichannel projects.
For instance:
![Screenshot of the Batch dashboard showing two omnichannel projects in a dropdown menu ("The Store" and "[DEV] The Store")](https://doc.batch.com/~gitbook/image?url=https%3A%2F%2F38998153-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FCL8wF0y1T2vLnm3yR2MW%252Fuploads%252FOnWV8i5ojTdvaTjdadTQ%252Ftechnical-guides_dev-live-env_02052025.png%3Falt%3Dmedia%26token%3D3b9efe5c-9054-44d9-b737-e5ed994ece61&width=768&dpr=4&quality=100&sign=1c305199&sv=2)
PreviousHow to trigger the native notification permission prompt on Firefox and Safari?NextHow can I include web push with my Content Security Policy rules?
Last updated
Was this helpful?