-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Playnite Web components as HASS addons #328
Conversation
Has a soft dependency on: #326 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution. I left some feedback and questions on the PR.
Also, @cvele , do you mind signing your commits? I'd prefer to have commits signed that enter the repo. Let me know if I can be any assistance in setting this up. Thanks! |
I am going to try to update this sometime today. |
package dev or specific version of images for use as HASS add-ons
PRs from external contributors do not have the PLAYNITE_TOOLBOX_URL available to them. For this reason, ci will fail to to package. Instead, check if the extension can be compiled and assume a successful compilation can be packaged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incredible work on this! This will help others that are already set up with Home-Assistant be able to use Playnite-Web. Thank you!
@andrew-codes This PR is highly opinionated regarding directory structure and naming conventions. It also assumes that different Docker images will be built for the add-ons, but based on the base Playnite web image. The main reason for this approach is the inclusion of Bashio, which is required to read configuration parameters set in Home Assistant.