| • East Coast meetup has 69 people signed up so far
|
| • Concerns about barbecue restaurant having enough meat for attendees
|
| • Solutions being considered to mitigate potential shortages, including preordering on the website and providing numbers beforehand
|
| • Importance of accurate headcount for planning purposes
|
| • Upcoming meetup in Raleigh, North Carolina on April 9th
|
| • Discussion of Docker performance issues on M1 Silicon Macs
|
| • Asahi Linux team's discovery about Apple's NVMe drivers being slow on macOS
|
| • Potential fix for Docker performance issue discovered by a community member and implemented by the Docker team
|
| • Linux installation on M1 Macs can be straightforward with minimal file system problems
|
| • Early benchmarks show good performance, except for GPU-heavy tasks
|
| • Jeff Geerling's video comparing power consumption between Ryzen and Mac Studio systems shows interesting results
|
| • Mac Studio has a significantly lower idle power draw (6 watts) compared to Ryzen systems (38-40 watts)
|
| • Discussion about fsync changes in Docker Desktop 2 and potential impact on data integrity
|
| • macOS "cheats" by only flushing writes to the drive itself, rather than also updating the file system tables
|
| • The user has experienced no issues with APFS and praises Apple's migration process
|
| • The user notes that APFS still lacks widespread adoption and production-grade usage in edge cases
|
| • The user expresses a desire to see more users deploying APFS in their own environments for it to be considered truly safe and reliable
|
| • The user recommends Linode as a cloud computing platform for server deployment, citing its ease of use and lack of lock-in
|
| • The user discloses a sponsorship arrangement with Linode and provides a promo code (linode.com/SSH)
|
| • The narrator discusses using Paperless-NG to manage digital documents and the recent development of a new project called Paperless-NGX.
|
| • Jonas Winkler took over the original Paperless project, but it was abandoned, leading to the creation of Paperless-NGX as a community-driven fork.
|
| • The current state of Paperless-NGX is that it has dropped support for Python 3.7 and Ansible playbooks, but updated documentation and containers.
|
| • The community is looking for contributors to help with ongoing maintenance and development, including updating Ansible playbook support.
|
| • The project is open-source and self-hosted, allowing users to escape the issues that come with commercial services going down.
|
| • Paperless NGX system
|
| • Implementing the system for tax season and expense tracking
|
| • Using scan apps to upload documents
|
| • Setting up ingestion rules for automatic tagging
|
| • Streamlining processes with Paperless, such as downloading PDFs and logging into separate systems
|
| • Matter Group's announced delay of the Matter Standard
|
| • Industry unity expected at launch
|
| • Chip shortages affecting smart home devices
|
| • Delayed release of Matter protocol causing uncertainty
|
| • Z-Wave integration issues and migration problems
|
| • Smart home setup disaster due to hardware and software incompatibilities
|
| • Advice to buy existing smart home devices rather than waiting for new technology
|
| • The speaker is considering redoing a Z-Wave JS migration due to the amount of work involved
|
| • They compare this situation to implementing a VLAN setup in their home, which would require a lot of effort and potentially lead to procrastination
|
| • The speaker recommends using tailscale.com/self-hosted for Zero Config VPN solutions that support up to 20 devices and can manage firewall rules
|
| • The benefits of tailscale include simplicity in setting up a mesh network between machines and supporting two-factor authentication, single sign-on, and the noise protocol used by WireGuard
|
| • Setting up bookmarks for Tailscale
|
| • Discussing the power of using Tailscale with multiple machines
|
| • Mentioning a potential new direction for duplicating (dupes) setups, specifically "no container theory"
|
| • Recapping current setup on Raspberry Pi 4s with Ubuntu 2004 and Home Assistant
|
| • Outlining issues with current setup, such as health states preventing updates
|
| • Considering alternative directions for future setup, including x86 machines with Proxmox
|
| • Running Home Assistant in a dedicated virtual machine
|
| • Considering an M1 Mac Mini as a headless home server running Linux
|
| • Identifying two main problems to solve with this next round: performance and reproducibility
|
| • Desiring reproducibility due to the difficulty of remembering current setup and potential future rebuilds
|
| • Evaluating Ansible for config management, but ultimately deciding against it in favor of Nix
|
| • Nix provides a way to build systems from config files
|
| • Using Nix OS is similar to using Nix as a package manager, but it offers more control over the system
|
| • Nix OS can build entire systems, including containers, with simple syntax
|
| • The Nix system figures out software dependencies and services automatically
|
| • Nix documentation provides reproducibility and ease of deployment
|
| • Nix is useful for containerized systems, such as Home Assistant and Plex
|
| • Nix allows for rolling updates and recreation of entire systems
|
| • The benefits of using Nix OS for managing systems and dependencies
|
| • Comparison between Nix OS and containerization (e.g. Docker)
|
| • Use cases where Nix OS's ability to manage entire software environments is beneficial
|
| • Concerns about the overhead of running an entire OS environment in a container
|
| • Isolating data and application stuff with Nix
|
| • Performance benefits of using M1 processors with Nix
|
| • Availability of Nix OS on M1 Mini devices
|
| • Comparison between Nix and container-based solutions (e.g. Ansible)
|
| • Reproducibility and redeployment capabilities of Nix
|
| • Ease of understanding and use of Nix's configuration language
|
| • Discussion on using Nix as a package manager for Linux systems
|
| • Comparison with Ansible and its role in deploying and managing systems
|
| • Nix's version control and reproducibility features
|
| • The potential future of Linux development and the adoption of Nix-like systems
|
| • Red Hat's Core OS operating system and Fedora Core OS as counterpoints to Nix
|
| • Upstream version of a system tried out
|
| • Configuration is done declaratively and through an ignition config file
|
| • NICs operate in a similar space to the operating system being read-only
|
| • Rolling back to a specific snapshot can be simple with ZFS backend storage
|
| • NICS has two methods: building and deploying without testing, or using a "build dash dash test" command that fails if it detects any issues
|
| • Discussion of using Nix for home automation
|
| • Comparison with Home Assistant core and potential minimal rebuild
|
| • Consideration of switching to Node-RED for automation
|
| • Transitioning to MQTT protocol
|
| • Managing data silos and integrating various systems (e.g. Z-Wave JS) through MQTT
|
| • Complexity of automations and programming logic
|
| • Comparison of Home Assistant vs Node-Red for automation
|
| • Use of MQTT protocol for power information from Victron system
|
| • Desire to rebuild and migrate existing automation systems
|
| • Plan to do a "bro build" episode with Wes at an RV
|
| • Plans for episode 70
|
| • Discussion about Panda Express and Chinese food preferences
|
| • Correction on the Argon Aeon 4-Bay Raspberry Pi NAS case price
|
| • Mention of temperature issues in the studio garage server room
|
| • Introduction to a Wi-Fi sensor built by Gene using ESP home
|
| • Home Assistant setup and monitoring
|
| • Fever app for video recording and integration with Frigate and Home Assistant
|
| • Bearded Tech's GitHub page and contribution to the community
|
| • Coral AI USB sticks and their increasing price (over $200)
|
| • Docker Compose for containerized applications
|
| • New project being worked on is mentioned as good and GPL-licensed
|
| • Host will be giving away Bitcoin to help with setting up Matrix
|
| • Upcoming AMA session at jblive.tv, March 31st
|
| • Mention of Fountain and its boost feature
|
| • Event for meetup in Raleigh on April 9th |
