Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add-On Software #227

Open
twa127 opened this issue Sep 25, 2021 · 1 comment
Open

Add-On Software #227

twa127 opened this issue Sep 25, 2021 · 1 comment

Comments

@twa127
Copy link
Contributor

twa127 commented Sep 25, 2021

Hi,

I'd like to clarify how I see that the 'Add-On' feature of MaxAir is intended to work:

  • MaxAir has basic functionality + the ability to add extra additional functions via the use of 'Add-On'
  • MaxAir should be configurable from the user interface (not the command line)
  • MaxAir 'Add-Ons' should not impact on system resources, if they are not installed, to avoid over burdening a hardware platform with limitted resources (particularly in the case of budget SBCs).
  • MaxAir 'Add-Ons' should, wherever possible, be self contained, they should not include changes to existing code modules.
  • MaxAir 'Add-Ons' are installed using the Install Software option in the System Configuration menu
  • Each 'Add-On' should include an install.sh, which installs any dependencies, installs any services required and installs the 'Add-On' itself
  • If new services are deployed as part of the installation, they should be included in the services section of ajax.php, in order that they can be managed from the user interface

An example deployment is for the Amazon Echo 'Add-On'
An example of what is not an 'Add-On' would be support for Tasmota devices.

@pihome-shc
Copy link
Owner

can we close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants