-
Notifications
You must be signed in to change notification settings - Fork 69
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
Centralized docker file for all use cases #200
Centralized docker file for all use cases #200
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #200 +/- ##
=======================================
Coverage 87.63% 87.63%
=======================================
Files 6 6
Lines 1707 1707
=======================================
Hits 1496 1496
Misses 211 211 ☔ View full report in Codecov by Sentry. |
@davidusb-geek , I have tested this as mutch as I could tonight. Published on both repos just in case you want to try it out on the weekend. Just note, its not fully tested. (struggling to test it inside of HA itself at the moment) |
Hi @GeoDerp, I really like this idea. |
Please update the branch. After merging #196 there is a conflict on the erased |
I think that the build step should be:
But not completely sure... |
Oh sure I didn't even think about GitHub Actions sorry. I'll wake up a little bit and help out 👍 |
I think you are right with this. Will have to find out. |
Just updating the docs now with the updated examples. This will replace the wiki development page. |
Ok I tested with docker standalone mode and there is this error:
|
Sorry @davidusb-geek, only just saw your reply. Ill have a look now |
Looks like a problem with the new template.html |
Yes maybe just need to copy that html fine when building the docker image. Sorry this is related to the PR #196 that was merged.. |
The optimization actually ran ok. |
The weird thing is that it works for me. |
Ill have a look at manually adding the files in and see if its happy then. |
Sorry @davidusb-geek I'm stumped. Hit a tired wall. Just committed the in progress documents for the Docker changes. Will have a look at the Docs and that bug in the morning, More then welcome to try and work it out if you like (and edit the docs). Sorry I couldn't get it working by this weekend. There is defiantly something weird going on with the /src/emhass/static files, I'm sure its something simple, I just cant work it out. (being in this tired state). |
I'm curious how you go if you try the docker in addon-local mode? If you still get template issue or style issues or neither. |
Hi. Ok I tested PR #196 merge and everything works fine.
I completely tested using the Docker standalone mode and tested the responsiveness on the wbeui, evertything is ok. This current PR #200 introduces a lot of changes on the Dockerfile and also the behavior of the add-on. |
I will refine the documents and fix the bugs and try and do a better job of explaining how the stages work. (And how emhass-add-on will operate) |
However for a quick reply, Entry point on the add-on default should be the add-ons run. The run script would have been called by the hidden entry point on the old docker, we are just removing the need to call the run script. |
sorry @davidusb-geek, there was defiantly some confusion with talking about the old and new versions of the Dockerfile yesterday. |
@davidusb-geek , okay i'm relativity happy with the results. Everything seems to work besides pip and git modes that require the git pull of this PR to work with the path changes. I have changed the path to /app by default as /data was being messed up with the mounts HA does for options.json on emhass-add-on. Let me know if you need any information on how they the PR works. Feel free to read the develop.md on emhass, and the test.md on emhass-add-on for some info on how to use the changes, |
Ok, will merge and test as soon as possible |
No stress at all 😁. Let me know if you need anything from me about this PR. Like if you want to discuss the comments on emhass-add-on pr. |
Testing this right now. Could it be possible to update the wiki contributing part to explain the new testing methods? The different build args options.. |
Ok nevermind, I just saw that great documentation that you made explaining everything in detail here: docs/develop.md |
One centralized Docker file for Add-on, Standalone & Add-on Testing
This uses a build argument build_version with values: addon, addon-pip, addon-git, addon-local standalone to determine what EMHASS mode you wish to build.
This hopefully helps simplifying testing by having a singular base environment for all docker work.
(Take advantage that requirements.txt exists and are different per repo)
(Still testing).