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
mini-graph-card: init at v0.9.3; mini-media-player: init at v1.8.1 #89136
Conversation
I think the easiest ways to manage those is to have home-assistant manage the whole |
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.
Sorry but 8000 lines of nix expressions for two simple home-assistant costum cards is too much. I would say either you can add those modules to our common pkgs/development/node-packages
node-modules` directory or they can be distributed in a separate repository (NUR?).
@@ -5209,6 +5209,10 @@ in | |||
|
|||
minetime = callPackage ../applications/office/minetime { }; | |||
|
|||
mini-graph-card = callPackage ../servers/home-assistant/lovelaceModules/mini-graph-card {}; | |||
|
|||
mini-media-player = callPackage ../servers/home-assistant/lovelaceModules/mini-media-player {}; |
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.
I would actually group packages like that into a common attribute set for better discoveribility, maybe hassCustomCards?
It could be similar to vimPlugins
or mpvScripts
or passExtension
.
@@ -0,0 +1,4 @@ | |||
[ | |||
{"mini-media-player": "git+https://github.com/kalkih/mini-media-player.git#v1.8.1" } |
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.
You should be able do drop this line into our node-packages
file as well.
I tried quickly to move it into nodePackages, but that's not really working, since the package needs it's development dependencies to be built and nodePackages (rightfully) don't include that. The npmjs version of these packages are immensly outdated, so I can track the git version. But then I'd need to overwrite Node is just a very dissatisfactory ecosystem. I'll probably try out NUR next. |
NUR repository up at https://github.com/mweinelt/nur-packages. |
Thanks. I still see value in having a common abstraction that makes it easy to add custom cards though! |
I documented this lovelaceModules stuff in the wiki: https://nixos.wiki/wiki/Home-assistant |
Thanks, though slight hickup. The internal webservers serving the
So do I, just not in this pull request. Same goes for themes. |
Motivation for this change
Gauging interest for integrating Home-Assistant custom lovelace modules, that are widely used within the hass community.
I'm currently installing them into home-assistant like this, something that could very well be abstracted away into a module option (thinking
services.home-assistant.lovelaceModules
) instead.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)CCing @dotlambda @globin @Mic92