Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
meta: build flags for plugins?
See original GitHub issueI was thinking that as the number of plugins for balenaSound grows, it may be that rather than just turning off a plugin using SOUND_DISABLE_PLUGIN options in balenaCloud, it might be better to have it so that you can add some kind of build flags / options that stop the builder from building certain plugins that you don’t need.
For example, by default it could add all plugins, but if you only needed the spotify and bluetooth plugins you could add --plugin spotify bluetooth or something like that. Or if you want to disable some plugins you could use --plugin-disable upnp roon for example.
This would have the added benefit of smaller image sizes being built and pulled down to the devices as well - meaning quicker builds and downloads/updates.
I am not sure if this is possible to do with flags, or perhaps via some environment variables on the application?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@tmigone I have a feeling I posted this somewhere in a FD thread about the CLI, but I can’t seem to find it now. Will see if I can dig it out!
@AlexProgrammerDE yeah I agree I think this has wider use cases than just balenaSound so probably makes more sense in the CLI
Would be nice to somehow deal with this through the balenaCloud dashboard when using the deploy button as well. So you can do it all without touching the terminal at all.