We use the concept of build configs to build different versions of the app. A build config defines for example the following aspects:
- Enabling and disabling of features
- Design, fonts, icons and theme colors
- Backend urls
- Override translations
- Store metadata
- integreat: Build config for Integreat.
- malte: Build config for Malte.
- aschaffenburg: Build config for Aschaffenburg
- integreat-test-cms: Build config for development using the test cms and with additional features enabled.
- integreat-e2e: Build config for E2E-Tests, primarily used in the CI.
NOTE: Testing and developing with the live cms instance should be avoided.
Therefore, the integreat-test-cms build config should be used primarily.
See the corresponding sections for native and web.
See the build config types for more information on structure, available options and their functionality.
Each build config is a set of javascript files (possibly including common files) that can be found in the corresponding directory. See the corresponding sections for native and web.
If you want to add more build configs in order to create a new whitelabelled app, have a look at the whitelabelling docu.