core: frontend: allow disabling core services #2868
Labels
core
Issue related to BlueOS-core
enhancement
New feature or request
triage
Needs triage from developers
ui
User Interface feature
Current behaviour
#2293 added functionality to avoid starting specific core services, but we can't set environment variables in core yet, and it's not nicely exposed to the user.
Some core services are not needed by every user, and while moving them to Extensions may be desirable longer term, it also seems worthwhile to allow the user to disable and re-enable core services when they want to, either for their standard usage or for testing/development purposes. As an example, it would be nice to be able to disable vehicle-related services while building a new firmware version, to provide extra CPU capacity, and they can then be re-enabled afterwards.
Expected or desired behaviour
startup.json
and have bootstrap read that when starting (but a dedicated UI would definitely be preferred)Prerequisites
The text was updated successfully, but these errors were encountered: