text stringlengths 7 369 |
|---|
[2625.06 --> 2627.88] You know, you guys really help us keep the show on the road. |
[2628.08 --> 2633.28] And you also give us the freedom to wait until a great sponsor like Tailscale comes along. |
[2633.68 --> 2637.36] You know, like you give us leverage there to make wise choices. |
[2637.56 --> 2639.52] You give us runways, they say in the business. |
[2640.08 --> 2642.34] Self-hosted.show slash SRE if you'd like to join. |
[2642.76 --> 2644.32] As a perk, you get more show. |
[2644.54 --> 2645.66] You get a post show. |
[2645.90 --> 2649.18] You can also support the entire network, just like the cost of two memberships. |
[2649.18 --> 2653.80] And you support all the shows and you get all the shows ad free, plus that post show. |
[2654.26 --> 2657.20] That network support is at jupiter.party. |
[2657.72 --> 2662.72] And as you all know by now, the place to go to get in touch with us is self-hosted.show slash contact. |
[2662.92 --> 2665.66] You can find me on the Discord at AlexKTZ. |
[2665.88 --> 2667.80] And you can find me on Matrix. |
[2667.98 --> 2669.64] Come join us in the self-hosted Matrix. |
[2670.28 --> 2673.28] Our Matrix server is colony.jupiterbroadcasting.com. |
[2673.40 --> 2674.62] And I didn't mention it in the show. |
[2674.78 --> 2675.92] And it's just a very quick addendum. |
[2676.10 --> 2678.74] Big thanks to Jake, the real orange one, the orange one, |
[2678.74 --> 2683.54] whatever his handle is this week, for running our Matrix party thing, |
[2683.64 --> 2685.38] setup party that we had a couple of weeks ago. |
[2685.82 --> 2686.36] Went really well. |
[2686.42 --> 2687.82] We had about 30 people show up. |
[2688.18 --> 2689.66] It was a fun time on a Sunday. |
[2689.86 --> 2692.32] So big thanks to Jake for setting that up. |
[2692.80 --> 2694.88] And as always, thanks for listening, everybody. |
[2695.08 --> 2697.52] That was self-hosted.show slash 65. |
• The host attended a meetup event in Raleigh and tried barbecue at the new meetup spot. |
• The event location was Nightdale Station, which has a park with a brewery, Texas-style barbecue joint, and local brewing company. |
• The host and his co-hosts are attending an upcoming East Coast meetup on April 9th in Raleigh (or more specifically, Nightdale). |
• The Raspberry Pi is celebrating its 10-year anniversary and the host reflects on how it helped him get involved with Linux. |
• Eben Upton, the founder of Raspberry Pi, launched the project expecting to sell only 1,000-5,000 units but has since sold millions. |
• Discussion of the Raspberry Pi's evolution over the past 10 years |
• The Pi's initial purpose in schools, its current status as a hobbyist-grade tinkerer device, and its widespread adoption |
• Eben Upton's mention of the Foundation putting two Pis on the International Space Station and other products using Pis in space |
• Criticism that the Raspberry Pi Foundation is not necessarily beholden to Linux community expectations, which has led to some issues with code drops and repository management |
• Discussion of the Pi's hardware being integrated into the mainline kernel and the importance of this development |
• Concerns about energy use and potential cost savings by optimizing setup configuration |
• Energy usage of old computers and hard drives |
• Comparison of energy prices (15p vs 50-60p per kilowatt hour) |
• Considerations for Raspberry Pi energy efficiency |
• Optimization for power savings over performance |
• Re-evaluation of storage needs and requirements |
• Simplification of systems with lower power consumption in mind |
• Reassessing personal performance requirements and priorities |
• Comparison of past computing capabilities (e.g. x86 box vs Raspberry Pi) |
• Discussing the cost and trade-offs of digital storage and data management (e.g. hard drive size, energy consumption) |
• Introducing Linode.com as a cloud hosting service with fast and reliable options |
• Exploring different plans and features available on Linode, including MVME PCIe storage and AMD epic CPUs |
• UI and dashboard features for system information |
• Recommendation for Wi-Fi based leak detection sensors |
• Comparison of Z-Wave and Zigbee options vs. Wi-Fi |
• Discussion of energy usage with Wi-Fi devices |
• Review of a specific Zigbee water sensor model |
• Promotion of supporting the show through subscription or donation |
• Discussion of Raspberry Pi projects, including a media center PC use case |
• The speaker talks about hooking up a device to a monitor in HDMI and using it for countdown clocks and IRC chatrooms |
• The Raspberry Pi was used for this purpose and became the basis for open source media center OSMC |
• A new case called the Eon, made by the company that makes the Argon case, is discussed on Kickstarter |
• The Eon case has a cyberpunk-inspired design with space-grade aluminum and can hold four SATA hard drives |
• The speaker mentions that the Eon case looks great but is pricey, costing $730 without the Raspberry Pi. |
• Cost of a budget machine with Pi and drives adds up to $1,500 |
• Consideration of long-term power savings (80% less) over 5 years |
• The Raspberry Pi 4 compute module is seen as an upgrade option |
• Carrier boards offer more connectivity options, such as PCI slots and SATA ports |
• The Argon Pi NAS should be its own carrier board with future-proofed components. |
• The speaker mentions that the GPIO pins on Raspberry Pi devices have remained largely unchanged since the first model. |
• They discuss the potential of the CM4 (Compute Module 4) and its application in various markets. |
• The speaker states that the current supply chain shortage has hindered adoption of the CM4, making it difficult to obtain. |
• They mention that they will not build a Pi-based server system without the CM4 and prefer using CM4 over standard Raspberry Pi for carrier boards. |
• The conversation turns to the personal collections of Raspberry Pis, with both speakers discussing their own numbers of devices. |
• The idea of building a giant Pi cluster is proposed. |
• The use case of Raspberry Pis as Kubernetes clusters like compute units is discussed. |
• Provisioning devices at scale |
• Raspberry Pi racks and their use cases |
• Kubernetes training and provisionning machines with a few clicks |
• Comparing the cost of using Raspberry Pis versus x86 boxes |
• Bare metal provisioning and fun projects with Raspberry Pis |
• The genesis of the Heimdall Docker dashboard |
• The speaker mentions using a home dashboard on their personal server and the proliferation of home dashboards in recent years |
• They mention setting up a Homer dashboard for their father, which allows him to access various services with ease |
• The speaker discusses other dashboard options, including Flame, which is highly customizable but lacks interactivity, and Organizer, which organizes apps behind tabs |
• They express concerns about technical debt and configuration drift affecting dashboard effectiveness |
• The speaker highlights the advantages of Flame's integration with Docker engine for live updates based on running containers |
• Tailscale is a zero-configuration VPN that installs on any device in minutes. |
• It's easy to manage firewall rules and access devices from anywhere. |
• The speaker uses Tailscale to connect their devices directly, using WireGuard and noise protocol encryption. |
• They appreciate the ease of creating a secure mesh network between servers, computers, and cloud instances. |
• Tailscale allows remote access with consistent IP addresses and device authentication. |
• Tailscale's flexibility in managing machines remotely |
• Ability to deauthorize machines without physical presence |
• DNS friendliness of Tailscale for easy network setup |
• User experience with camera systems, including Blue Iris |
• Importance of monitoring and backups, particularly for server snapshots |
• Discussion of a listener's fix for damaged wiring in a project |
• The user is seeking a tool to read snapshot logs and send an email in case of an error |
• Health checks.io is mentioned as a possible solution for monitoring cron jobs and detecting errors |
• The user describes how health checks can be used to ping a server, append logs, and monitor job duration |
• The self-hosted version of health checks is also discussed |
• The importance of keeping the system simple and not over-complicating it with unnecessary features |
• A listener, Norm, writes in to express appreciation for the show and offers support by purchasing a membership. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.