VIP Local Development Environment limitations
Some features are not yet available in the local environment or have default behaviors that differ from a VIP Platform environment.
- The VIP File System and Page cache services are not built in. When developing features for an application that rely on these services, it is strongly recommended to stage changes and perform tests on a non-production VIP Platform environment.
- By default, the NGINX HTTP Concat plugin that handles file concatenation and minification is disabled on a VIP Local Development Environment but can be optionally code-enabled.
Note
The VIP Local Development Environment is optimized for building features, testing plugin and software updates, and fixing bugs during early development. It is not intended to fully replicate the architecture, infrastructure, or performance of environments on the VIP Platform.
Performance testing for application code should be conducted on a non-production VIP Platform environment rather than on a VIP Local Development Environment. A non-production environment shares the same architecture as production, so testing—including load tests—on non-production will provide a more accurate indication of code performance.
Testing in a non-production environment helps to expose potential performance issues earlier and increase confidence that deployments to production will behave as expected.
Last updated: October 21, 2025