pyscript
nixpkgs
Our great sponsors
pyscript | nixpkgs | |
---|---|---|
7 | 973 | |
774 | 15,656 | |
2.6% | 5.3% | |
6.6 | 10.0 | |
22 days ago | about 22 hours ago | |
Python | Nix | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pyscript
-
Building a local AI smart Home Assistant
3) Again, already there. ESPHome is a first class citizen in HA.
I feel like you've not read the HA docs [1,] or took the time to understand the architecture [2]. And, for someone who has more than enough self-proclaimed skills, this should be a very understandable system.
[0] https://github.com/custom-components/pyscript
- Run Your Home on a Raspberry Pi
-
Anyone tried Apache Airflow to automate?
I see someone else mentioned AppDaemon. I would try out pyscript first ( https://github.com/custom-components/pyscript ). It is just a some HACS install, and then you are good to go.
- Home Assistant – open-source home automation
-
Python script not working
I highly recommend using this instead of the pretty awful built-in Python thing. Pyscript is just a TON better.
-
Useful Routine to Update Volume on All Speakers to Normal Levels
Sure! I use pyscript for the automation; here's the wiki page I made.
-
What would you like to see in 2021 for Home Assistant?
Sounds like you might enjoy using Pyscript to write your automations. I also found Node-Red to be frustrating when I was starting off; Pyscript let's you write Python for everything and is super easy to follow IMO.
nixpkgs
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
-
GitHub Disabled the Xz Repo
True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)
It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.
That is the problem.
-
Combining Nix with Terraform for better DevOps
We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.
What are some alternatives?
appdaemon - :page_facing_up: Python Apps for Home Automation
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
home-assistant-remote - Links multiple home-assistant instances together [Moved to: https://github.com/custom-components/remote_homeassistant]
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
remote_homeassistant - Links multiple home-assistant instances together
git-lfs - Git extension for versioning large files
midea-ac-py - This is a library to allow communicating to a Midea appliance via the Midea cloud.
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
operating-system - :beginner: Home Assistant Operating System
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
meross-homeassistant - Custom component that leverages the Meross IoT library to integrate with Homeassistant
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.