What’s New
Getting Started

Publishing & Environments

Last Updated: November 2, 20240.7 min read

Environments

ngine is built with the concept of target environments in mind. An environment is typically tied to backend services and platform. We expose three environments by default: Development, Staging and Live.
For example, by default builds pushed to Apple TestFlight are configured to use the staging environment. This coincides with purchasing being in sandbox mode for TestFlight apps.
The flow for ngine and derivative apps ends up being: development ➝ staging (such as Apple TestFlight, in order to confirm a release candidate’s stability) ➝ release.

Switching Environments at runtime

The -environment switch can be used on desktop to switch between different environments at runtime. For example -environment staging would switch to the staging environment for that session.

Feedback

Please be sure to submit issues or feature requests through the embedded feedback form. In the event it is a major issue please contact us directly through Discord.