text stringlengths 0 1.8k |
|---|
• Understanding GitHub's infrastructure and lack of agnosticism in dev environments |
• Suggesting alternative cloud spaces options, such as Gitpod |
• The speaker wants to discuss using GitHub Code Spaces for development environments. |
• They mention wanting to partner with GitHub and have them sponsor Changelog's use of Code Spaces. |
• The speaker prefers using a pre-built, automated dev environment over setting up their own local machine. |
• They express frustration with managing upgrades on their local machine and the potential for conflicts between personal projects and work-related development environments. |
• The speaker considers an electric vehicle analogy to describe their desire for a "prescribed dev space" that is easy to use and doesn't require them to manage upgrades or configurations. |
• They discuss the importance of identity and access control in such a dev environment. |
• A short-term solution suggested is using Code Spaces as it currently exists, with the hope of future improvements. |
• Discussion of using GitHub Code Spaces as a solution for the Changelog app |
• Comparison with Gitpod and Equinix Metal |
• Planning for a future episode on GitHub Code Spaces in December |
• Short-term solution: brew install Elixir, brew install Postgres, clone the repo (rejected) |
• Alternative short-term solution: use Code Spaces wrapped in a bow (GitHub-provided infrastructure) |
• Shipping delays for new MacBooks |
• Using old machines as a temporary solution |
• Uploading to cloud storage (specifically S3) |
• Prioritizing tasks due to limited time and GitHub issues |
• Bug fix: newsletter links proxy encodes special URLs with HTML instead of percent based |
• Apostrophe in URL causing encoding issue |
• The speaker is investigating an issue with a web framework, specifically Elixir Phoenix, where an apostrophe in a URL is causing HTML encoding instead of URL encoding. |
• They consider it a dependency issue and seek advice on how to proceed from Gerhard. |
• Gerhard suggests checking for issues in the repository, looking at code changes around the problem area, and opening an issue if necessary. |
• The speaker questions whether this is actually a bug or just expected behavior. |
• They decide to upgrade all dependencies, including Phoenix, rather than addressing the specific issue directly. |
• The upgrade process reveals breaking changes in the new version of Phoenix that were not anticipated by the speaker. |
• Upgrading from Phoenix 1.5 to 1.6 caused issues with API changes |
• Two specific keys in the "assigns" data bag were removed: view module and view template |
• The removal caused metadata issues on the entire site, including Twitter embeds and third-party integrations |
• The developer had to refactor the meta module and fix several hours of work |
• A yak was shaved (in a humorous analogy) |
• Upgrading or replacing Ingress Nginx with Traffic |
• External DNS management |
• Honeycomb Agent and other agents' setup |
• The yak shaving problem: getting stuck in a cycle of small tasks leading to more work |
• State of flow and perseverance in completing tasks |
• Overconsumption of time on non-priority tasks during a state of flow |
• Mention of multiple gifts and projects |
• Discussion of using cross-plane to manage infrastructure |
• Benefits of integrating various tools, including Dagger and Honeycomb |
• Importance of giving feedback to improve products |
• Storytelling approach in the podcast and its benefits |
• Connection between the creators and users of certain projects (e.g. Solomon Hikes) |
• Reflection on the "circle of life" and serendipity in collaborations |
• Discussing feedback and suggestions for various tools, including Honeycomb, Dagger, Crossplane, and Grafana Cloud |
• Importance of observability in the CDN and its benefits |
• Concept of "an and proposition" rather than "either or" when choosing tools with different strengths and weaknesses |
• Understanding trade-offs between different tools and not looking for a single "perfect" tool |
• Upcoming episodes and topics, including contributions from Echoes initiative |
• Discussion of user experience and the importance of a patient and knowledgeable approach |
• Introduction to Kaizen and its application in improving processes |
• Expression of gratitude to team members, listeners, and partners |
• Announcement of future plans for the podcast and community |
• Promotion of the changelog.com website and community |
• Closing remarks and preview of upcoming episodes |
• The show's previous recording was cut due to a humorous and uncontrollable break caused by Gerhard's reaction to Jared's yak shave story. |
• Gerhard spent three weeks resolving his home network setup issues with multiple routers, internet connections, and physical installations. |
• He now has two fiber connections, two ISPs, and additional holes in his walls. |
• The conversation focuses on the absurdity and dedication required for such an extreme case of yak shaving. |
• Discussion of WAN connections and network setup |
• Mention of budgeting and new equipment purchases |
• Use of specific software tools, including Gitpod and Codefaces |
• Reference to movie "Contact" and the phrase "you can never have too many" |
• Humorous exchange about wanting multiple copies of a person (Gerhard's wife) |
[0.08 --> 6.06] You are listening to ShipIt, a podcast about operations, infrastructure, and the people |
[6.06 --> 7.86] that keep all those lights blinking. |
[8.58 --> 13.56] I'm your host, Gerhard Lazy, and this is our third Kaizen with Adam and Jared. |
[14.00 --> 19.90] We combine all our learnings from the previous 10 episodes, ship them in changelog.com, and |
[19.90 --> 21.72] see if they make things better. |
[22.26 --> 27.14] Today, we talk about how we're adding GitOps the wrong way, asking questions with Honeycomb |
[27.14 --> 32.10] and realizing that we must be holding our CDN wrong, and Jared tells us about the work |
[32.10 --> 37.96] that he has been doing to move all our static files from regular volumes to an S3-like object |
[37.96 --> 38.26] store. |
[38.58 --> 43.38] If you like a good yak shave, listening to this one is a lot more fun than doing it. |
[43.78 --> 48.18] The thing which I'm most excited about are the Christmas gifts that we have been preparing |
[48.18 --> 48.60] for you. |
[49.04 --> 54.04] While GitHub Codespaces is not going to be part of the upcoming Christmas special, today we |
[54.04 --> 56.54] talk why we must invest in a Codespaces integration. |
[56.54 --> 60.42] Changelog 459 and Backstage 20 are related. |
[60.92 --> 64.38] Big thanks to our partners Fastly, LaunchDarkly, and Linode. |
[64.70 --> 66.42] Thank you for the great bend with Fastly. |
[66.76 --> 68.60] You can learn more at Fastly.com. |
[69.08 --> 73.34] Ship new features with confidence by getting your feature flags powered by LaunchDarkly.com. |
[73.68 --> 76.88] And thank you Linode for keeping our Kubernetes fast and simple. |
[77.30 --> 81.12] Run your setup as we do via linode.com forward slash changelog. |
[86.54 --> 88.18] What's up shippers? |
[88.32 --> 91.64] This episode is brought to you by our friends at Fly. |
[92.08 --> 96.10] Fly lets you deploy your apps and databases close to your users in minutes. |
[96.38 --> 103.88] You can run your Ruby, Go, Node, Dino, Python, or Elixir app and databases all over the world. |
[104.06 --> 104.86] No ops required. |
[104.92 --> 108.00] Fly's vision is that all apps should run close to their users. |
[108.00 --> 112.92] They have generous free tiers for most services so you can easily prove to yourself and your team |
[112.92 --> 116.10] that the Fly platform has everything you need to run your app globally. |
[116.52 --> 121.16] Learn more at fly.io slash changelog and check out the speedrun and their excellent docs. |
[121.56 --> 124.90] Again, fly.io slash changelog or check the show notes for links. |
[124.90 --> 132.00] We are going to ship in 3, 2, 1. |
[145.62 --> 148.72] So we're back for the third Kaizen. |
[149.46 --> 152.40] I can't believe it's been 30 episodes and I'm not the only one. |
[152.40 --> 155.84] Adam can't believe either that it's been 30 episodes of Ship It. |
[156.14 --> 156.40] Yeah. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.