# blog-post Published articles for blog-post. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cargo-dyndrv: A new way of building Cargo packages with Nix DevFeed: [Cargo-dyndrv: A new way of building Cargo packages with Nix]() Original publisher: [Read original article]() Author: Ericson2314 Published: 2026-09-16T20:13:36Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Rust](), [systems]() Tags: [announcements](), [blog-post](), [declarative](), [rust]() ### AI overview The article introduces cargo-dyndrv, a new way to build Cargo projects with Nix. It uses dynamic derivations for per-crate incrementality and Cargo's unit graph to align operations with Cargo, while trading some flexibility for fidelity and forward compatibility. ### Source excerpt Obsidian Systems - 16 Sep 26 cargo-dyndrv: A Beginning Building Rust within Nix has always been somewhat of an annoying problem. Nixpkgs includes tools like buildRustCrate to build a single crate and buildRustPackage to build an entire project with all its dependencies, but both have substantial issues:... We have a new way way of building Cargo projects! As the blog post describes, what distinguishes this from all the other ways of building Cargo project in Nix is this combination of methods: Uses dynamic derivations, so no eval time penalty for per-crate incrementality Uses Cargo's unit graph, so we automatically match to how Cargo performs operations Both cargo-dyndrv itself and this blog post about it are all @artemist's work; I am only the one posting it because she has already left for NixCon (see you all there!) and I haven't left yet, so my internet connection is better. Finally, thank you for Saronic for collaborating with us on this project. 6 posts - 5 participants Read full topic ## The Great Python Refactor of 2017 And Also 2018 DevFeed: [The Great Python Refactor of 2017 And Also 2018]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-03-19T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Python](), [Refactoring](), [Code](), [Development](), [Tool]() Tags: [2017](), [blog-post](), [code](), [dev](), [engineering](), [infrastructure](), [news](), [python](), [refactor](), [refactoring]() ### AI overview This first article in a series describes Khan Academy's 2017-2018 Python refactoring effort. It explains how an overloaded codebase structure developed, the changes made to organize files and directories, and the difficulties of the work. ### Source excerpt By Craig Silverstein Our codebase was a mess. One day, we decided to do something about it: namely, ... Read more ## Kotlin on the server at Khan Academy DevFeed: [Kotlin on the server at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-06-28T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Kotlin](), [backend-development](), [Python](), [Google]() Tags: [api](), [bigquery](), [blog-post](), [developer-experience](), [engineering](), [google](), [http](), [infrastructure](), [java](), [kotlin](), [news](), [python](), [server-side-development]() ### AI overview Khan Academy describes testing Kotlin for user-facing server requests during a 2018 hackathon and deciding to adopt Kotlin as a second server-side language after reporting positive efficiency results and a positive developer experience. ### Source excerpt By Colin Fuller At Khan Academy, we run our web application using Python 2.7 on Google's App Engine ... Read more ## Stories from our latest intern class DevFeed: [Stories from our latest intern class]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-12-21T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Programming](), [Mobile](), [JavaScript](), [Ionic](), [AdventureX 2026]() Tags: [backup](), [blog-post](), [email](), [engineering](), [github](), [hackathon](), [intern](), [ionic](), [javascript](), [mobile](), [news](), [programming](), [project](), [stories](), [web-frontend]() ### AI overview This article shares reflections from Khan Academy's 2015 intern class. It describes a hackathon project that used Ionic to build a mobile app for browsing and playing JavaScript projects, and discusses backing up Khan Academy mailing-list data. ### Source excerpt By 2015 Interns We sent an email out to all of the 2015 interns in early November, shortly ... Read more ## Vondra: PostgreSQL development activity DevFeed: [Vondra: PostgreSQL development activity]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-15T13:20:30Z Content type: news Language: en Sources: [LWN.net]() Topics: [PostgreSQL](), [Development]() Tags: [blog-post](), [development](), [postgresql]() ### AI overview A PostgreSQL contributor's analysis examines development activity from the late 1990s to the present. It reports roughly 50 commits per week today, compared with about 25 per week around 2010, alongside an approximately twofold increase in active committers. ### Source excerpt PostgreSQL contributor Tomas Vondra has published a blog post looking at development activity in the project, with data from the late 1990s to today. We're doing ~50 commits per week, give or take. In ~2010 we were doing maybe 25/week, and the trend seems to be a slow and consistent growth. The monthly average makes the trend a bit easier to spot. Which is good, although there's a lot of other important details (size of commits, are they new features or fixes, ...). It however nicely aligns with the number of active committers, which also grew ~2x between 2010 and today. So maybe that's working as expected. ## Decoding cosmic signals with deep learning and Keras DevFeed: [Decoding cosmic signals with deep learning and Keras]() Original publisher: [Read original article]() Author: Yufeng Guo; Jonas Glombitza, PhD Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Deep learning](), [Keras](), [data]() Tags: [analysis](), [blog-post](), [data](), [deep-learning](), [keras](), [particle-physics](), [physics](), [research]() ### AI overview The article explains how deep learning and Keras can help analyze the enormous, complex datasets produced by astroparticle-physics observatories. These methods may improve instrument sensitivity, reveal hidden patterns, and identify anomalies in signals from cosmic messengers such as photons, neutrinos, and cosmic rays. ### Source excerpt Astroparticle physics sits at the exciting intersection of astrophysics and particle physics and stu... ## VCF Breakroom Chats Episode 94: Supercharging VKS Networking with Tigera DevFeed: [VCF Breakroom Chats Episode 94: Supercharging VKS Networking with Tigera]() Original publisher: [Read original article]() Author: anika suri Published: 2026-09-08T20:45:36Z Content type: article Language: en Sources: [VMware Blogs]() Topics: [Kubernetes](), [networking](), [Security](), [DevOps]() Tags: [blog-post](), [breakroom-chats](), [devops](), [ecosystem](), [kubernetes](), [networking](), [partners](), [security](), [vmware]() ### AI overview This episode of VCF Breakroom Chats discusses Kubernetes networking and security in production with Abhishek Rao from Tigera, the company behind Project Calico. It also highlights partnership resources and is aimed at IT practitioners, platform professionals, developers, DevOps professionals, and AI/ML professionals. ### Source excerpt In this episode of VCF Breakroom Chats, Anika Suri sits down with Abhishek Rao from Tigera, the company behind Project Calico, to discuss a critical aspect of running Kubernetes in production: networking and security. Want to learn more about this partnership? Check out the Kubernetes Ecosystem Partners page for more resources. Read this blog post. About ... Continued The post VCF Breakroom Chats Episode 94: Supercharging VKS Networking with Tigera appeared first on VMware Blogs. ## Please Help Me Follow Your Content DevFeed: [Please Help Me Follow Your Content]() Original publisher: [Read original article]() Published: 2026-09-04T05:37:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [RSS Feed](), [Web Development]() Tags: [blog-post](), [html](), [rss]() ### AI overview The author argues that email updates and RSS feeds are reliable ways to follow worthwhile blog content, unlike engagement-driven social media algorithms. They urge creators using static website generators to enable or add an RSS feed. ### Source excerpt Finding good content in the swamp of AI slop is hard, and whenever I find a blog post worth reading, I'd like to know when the author publishes the next one. For stupid reasons (like a day having only 24 hours, and me having a life), I can't periodically scan all websites I find interesting, but fortunately, I don't have to. Two well-known mechanisms work reliably: email updates and RSS feeds. Read more ... ## Benchmarking vector indexes DevFeed: [Benchmarking vector indexes]() Original publisher: [Read original article]() Author: Evgeniy Patlan Published: 2026-08-27T13:35:32Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [benchmarking](), [Ground truth / benchmark quality](), [Databases](), [ann](), [datasets](), [Sorting]() Tags: [ai-vector](), [ann](), [benchmark](), [benchmarking](), [benchmarks](), [blog](), [blog-post](), [data](), [database-performance](), [database-trends](), [databases](), [datasets](), [embeddings](), [index](), [measurements](), [model](), [open-source](), [percona](), [points](), [report](), [run](), [search](), [sorting](), [vector-search](), [vectorsearch]() ### AI overview This article explains how Percona's vector-bench measures vector indexes by building database engines from pinned versions, running them in identical containers with the same data and hardware, and comparing consistent measurements. It describes embeddings, exact search, approximate nearest neighbour search, and ground truth as the brute-force reference needed to evaluate index accuracy. ### Source excerpt Nearly every database has vector search now, and every one of them has a blog post with a big number in it. Almost none of those numbers can be checked, because the thing that makes them meaningful is usually missing. We built a vector-bench to stop guessing. You name the engines you want, build them ... Continued The post Benchmarking vector indexes appeared first on Percona. ## Worth Reading: On AI Coding and Its Discontents DevFeed: [Worth Reading: On AI Coding and Its Discontents]() Original publisher: [Read original article]() Published: 2026-08-19T06:24:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [ai-coding](), [coding](), [Code]() Tags: [agentic](), [ai](), [ai-coding](), [blog-post](), [coding](), [development](), [worth-reading]() ### AI overview The article argues that AI coding tools should not be treated like traditional compilers. Unlike deterministic, mature compilers, AI coding tools can produce bugs, and agentic loops do not eliminate that reliability gap. It points readers to Cal Newport's discussion of the drawbacks of AI-assisted coding. ### Source excerpt A lot of AI-coding enthusiasts are making claims along the lines of "AI coding tools are like compilers; you supply intent, they translate it into code, and who ever looked at the machine-code output?" Unfortunately, there is a bit of a gap between hope and reality; traditional compilers were always deterministic, and are (after decades of development and bug-fixing) pretty much bug-free. AI coding tools are neither, and no amount of "agentic loops" will solve that. Read more ... ## \[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released DevFeed: [\[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released]() Original publisher: [Read original article]() Author: Patrick Donnelly Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [releases](), [Authentication](), [Linux](), [client](), [monitor]() Tags: [authentication](), [blog-post](), [cve](), [cves](), [en-article](), [en-blog-post](), [errors](), [linux](), [process](), [release](), [releases](), [rest](), [rgw](), [squid](), [tentacle](), [upgrade]() ### AI overview The Ceph project released Tentacle 20.2.4 and Squid 19.2.6 as hotfixes addressing four CVEs. The article urgently recommends upgrading and explains changes to CephX key types, daemon-key rotation, authentication controls, recovery procedures, and multisite RGW request signing. ### Source excerpt The Ceph project has released Tentacle 20.2.4 and Squid 19.2.6 hotfixes for four CVEs across several components. This is the sixth backport release in the Squid series. This is the fourth backport release in the Tentacle series. We strongly recommend that all Ceph operators upgrade to one of these releases as soon as possible. Release Date ¶ August 19, 2026 Critical Upgrade Steps ¶ The fix for CVE-2025-30156 introduces a new CephX key type, aes256k. This is the first time Ceph has introduced a new key type for CephX credentials. Therefore, a new procedure exists for upgrading and rotating Ceph daemon keys as part of this CVE. Before upgrading a Ceph cluster, the operator should familiarize themselves with the procedure to upgrade CephX keys. These steps are for package-based deployments of Ceph. In other sections, the document also includes new information about key rotation procedures, monitor authentication controls, and emergency recovery procedures. Deployments using cephadm will automate the process except for client keys. You may notice that Cephadm spends more time than normal on the upgrade after updating all daemon images. This is due to a new process rotating the OSD and MDS keys. Please be patient. There are plans to improve this in the future. Deployments using Rook will also automate rotation of some client keys with some exclusions. Look to the Rook project's announcement for more details. Client and kernel upgrades are recommended to support aes256k. Note that upstream Linux kernel client support began in kernel 7.0 and has been backported to CentOS Stream 9 and 10. Check with your distribution vendor for backported key support before rotating client keys used by the kernel. As part of upgrading a Ceph cluster, six new health warnings and errors will be generated. This is normal. As part of the process to upgrade/rotate entity keys, you will address the warnings and errors as you go. These are documented beginning here. The CephX documentation has bee ## Exploring the BGP Neighbor CONNECT State DevFeed: [Exploring the BGP Neighbor CONNECT State]() Original publisher: [Read original article]() Published: 2026-08-18T05:16:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [networking](), [Finite-state machine](), [Routing (disambiguation)]() Tags: [bgp](), [blog-post](), [debug](), [routing]() ### AI overview An exploration of how Cisco IOS/XE presents the BGP neighbor CONNECT state during an incoming TCP session. The article tests several lab scenarios involving passive neighbors, static discard routes, ACLs, and suppressed ICMP unreachable messages, finding that CONNECT appears in BGP debugging output while the neighbor remains Idle in the displayed operational state. ### Source excerpt Sakar left an interesting comment on my The Curious Case of the BGP Connect State blog post, claiming that Cisco IOS/XE goes through a CONNECT state when opening an incoming BGP session. I wanted to double-check this behavior, so I needed a scenario where one router would keep sending TCP SYN requests, the other would not (or we wouldn't learn anything), and the two routers could not communicate (or they'd quickly go into the OPEN state). Here's my first attempt at meeting those requirements: Read more ... ## Compress netlab Lab Topologies with Dot Notation DevFeed: [Compress netlab Lab Topologies with Dot Notation]() Original publisher: [Read original article]() Published: 2026-08-12T05:55:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Python](), [YAML](), [BGP]() Tags: [bgp](), [blog](), [blog-post](), [netlab](), [post](), [python]() ### AI overview An article about using Python Box dotted notation to make netlab lab topology definitions easier to read and more concise, including examples in YAML for BGP routers and IPv4 links. ### Source excerpt netlab is using the Python Box library to make the code easier to read1. When I started the project, I hated the way you fetch values from Python dictionaries with stuff like node['ospf']['area']; Python Box lets you write node.ospf.area. Even better2, you can tell Python Box to create intermediate dictionaries as needed. node.ospf.area = 1 will automatically create the node.ospf dictionary. But wait, there's more (yes, we're getting to the topic of today's blog post): Box lets you use the same dotted notation in YAML files. Read more ... ## Why the author is using slash pages on Snook.ca DevFeed: [Why the author is using slash pages on Snook.ca]() Original publisher: [Read original article]() Published: 2026-08-07T00:00:00Z Content type: opinion Language: en Sources: [Jonathan Snook]() Topics: [RSS]() Tags: [blog-post](), [rss]() ### AI overview The author introduces the RSS Club on Snook.ca and explains the purpose of slash pages such as /now and /where. The post describes them as a way to share current activities and relevant site information without requiring extensive background, and notes the addition of a privacy policy. ### Source excerpt Hey, it's the inaugural post for the RSS Club on Snook.ca! I was working away on my site, adding content that I thought might be relevant to some, like an AI statement and a privacy policy. Most people probably don't care but for those that do, it's there and it shows that I care about those things, too. I never really had a name for these types of one-off pages but I came across slash pages and with this redesign, I've been considering what felt relevant to include or not include on my own site. Why Now? Some of the items like /now seem like they should be actual blog posts. Like this one. This is what I'm thinking about now. My next blog post will be about what I'm thinking about then, which will be now. Want to know what I'm up to right now? I'm writing now. But when you read this, I'll no longer be writing this. I'll be doing something else. Maybe I'm sleeping, or making coffee, or out walking somewhere, or sitting on the toilet. Why Not? I realize I'm being silly. Sometimes it's nice to catch up with what somebody is up to. It's answering the question, "hey what're you up to these days?" It's surfacing information without requiring people to understand the entire lore about what led you to this moment in time. For example, I subscribe to a couple newsletters that are like a /where page. They update people on their travels while also giving a life update around why they might be on a particular trip, or why they might be at home. Maybe my friends would like to hit up my /where page to see where I might be given all my travels. (I don't have a /where page.) Slash away For now, I have my slash pages plus a couple undocumented ones like my old /speaking page that remains more like a historic artifact found just under the surface. Today, I added my privacy policy. I think that'll be it for now. Have something to say? Tell me about it. ## v20.2.3 Tentacle released DevFeed: [v20.2.3 Tentacle released]() Original publisher: [Read original article]() Author: Yuri Weinstein Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [Deployment](), [Server](), [Hardware](), [TLS (Transport Layer Security)](), [Kafka](), [Grafana Cloud Metrics](), [Monitoring](), [Command-line interface](), [IO]() Tags: [2026](), [authentication](), [blog-post](), [cli](), [en-article](), [en-blog-post](), [hardware](), [io](), [kafka](), [metrics](), [monitoring](), [release](), [storage](), [tentacle](), [tls]() ### AI overview Ceph v20.2.3, the third minor release in the Tentacle series, is a recommended update containing fixes and improvements across metadata servers, object storage daemons, RADOS Gateway, client libraries, the dashboard, ceph-volume, and NVMe-oF. Changes include storage reliability fixes, TLS 1.3 cipher customization, encrypted object copying, Kafka notification authentication, hardware monitoring, CSV host uploads, and role-management updates. ### Source excerpt This is the third minor release in the Tentacle series. We recommend that all users update to this release. Release Date ¶ August 5, 2026 Notable Changes ¶ MDS (Metadata Server) ¶ Fixed a crash and shutdown hang that could occur when ephemeral pins were active and max_mds was set to 0. Session reclaim could miss blocklisting an old session; this is now handled correctly. Fixed a case where scrub was unable to identify damage from an irreparable hard link. OSD (Object Storage Daemon) ¶ BlueStore: Fixed a BlueFS WAL envelope-mode bug that caused write buffer misalignment. Erasure Coding: Fixed truncate+write planning for EC shard sizes. Fixed a condition that prevented rolling forward of PG log entries. Prevented OSDMap::check_health() from asserting when new OSDs are found in a subtree. Scrub: "repairing" scrubs -- deep scrubs re-run specifically to fix a previously detected inconsistency -- are no longer blocked by the configured allowed scrub hours/days; they can now run at any time. RGW (RADOS Gateway) ¶ Added the ssl_ciphersuites option for the Beast front-end to support TLS 1.3 cipher customization. Fixed PutObject's canned_acl comparison bug affecting BlockPublicAcls. Fixed crashes occurring on realm reload. Implemented CopyObject support for encrypted objects. Added mTLS client-certificate authentication support for Kafka notifications. Fixed removal of delete markers in lifecycle processing. RADOS / librados / neorados ¶ neorados: Fixed an infinite trim loop on empty data log shards. Fixed cancellation-slot cleanup in librados/asio's associated executor. Dashboard ¶ Added a hardware-monitoring dashboard backed by node-proxy metrics. Fixed a bind-address regression caused by CherryPy isolation. Added support for adding hosts via CSV upload. NVMeoF: multiple CLI and UI backports (EC pool support, IO statistics, role management). Object: The global RGW Roles tab has been removed. Role management is now scoped under RGW Accounts, where roles can be listed, created, ## Secret RSS Posts DevFeed: [Secret RSS Posts]() Original publisher: [Read original article]() Published: 2026-08-04T00:00:00Z Content type: opinion Language: en Sources: [Jonathan Snook]() Topics: [RSS Feed](), [Web]() Tags: [blog-post](), [posts](), [rss](), [technical]() ### AI overview The author introduces an RSS Club for posts that appear in the RSS feed without being linked from the site's home or index pages. The article explains how 11ty collections and tags control whether content appears in the RSS feed, on the site, or in both. ### Source excerpt I've seen Dave Rupert do posts that only appear in the RSS feed. He called it the RSS Club. In his words, It's like a newsletter delivered to your feed reader to celebrate the medium of RSS and breakaway from social media. I like that ethos and am choosing to do the same. What posts will qualify as part of the RSS Club remains to be seen. Maybe they'll be more personal. Maybe they'll cover topics that don't need to be directly linked from home pages and index pages. Maybe I'll get bored of the idea and we never hear of this again. And it's not like they'll be sooper-dooper secret because there will still be a web page that will be generated. You could still share and link the page, if you wanted. At least, for now. It's just that they won't be linked to from any of the index pages. Perhaps one day I'll look into creating content purely for the RSS feed that doesn't have a permalink generated for it. That'll require some tweaks to the RSS feed since it relies on the URL for things like the ID. Consider this an invitation to subscribe to the RSS feed--if you haven't already--and perhaps some interesting content will find it's way to you. Technical Bits This site is built with 11ty. Every file--okay, not every file; I'm simplifying here--gets added to a collection. Files can be added to a specific collection using tags. When I first built this site, every blog post was tagged as a post. Then, I told the home page to grab the most recent posts. And the index view to grab all of the posts. And then the RSS feed should grab the ten most recent posts. What I've done is added a new collection called rss and I changed the RSS feed to only grab items from the rss collection. tags: - post - rss This allows me to create content that only appears in the RSS feed or only appears on the site or appears in both. This system will be used for any new thing that I add. For example, if I add photography, I can create a photo tag and add the photos to the RSS feed or choose not to. I can ad ## Technical Development of The Incident at Galley House DevFeed: [Technical Development of The Incident at Galley House]() Original publisher: [Read original article]() Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [Development](), [HTML](), [Web Development](), [interface](), [Game engine]() Tags: [blog-post](), [development](), [game](), [html](), [interface](), [steam](), [technical]() ### AI overview A technical development post about The Incident at Galley House, covering its origins as a Twine and HTML prototype, iterative content and puzzle testing, and adaptation of its typing-based gameplay for a controller interface. ### Source excerpt Evil Trout's second game, The Incident at Galley House, is out now on Steam! Last year, after The Roottrees are Dead shipped, I wrote a technical blog post about its development, which was well received, so I decided to do the same thing for this game. Note: The images in this post have minor spoilers for the beginning of the game. If you want to be 100% spoiler free, now's your chance to run away. ## Runtime security monitoring and threat detection: Protecting production without slowing developers DevFeed: [Runtime security monitoring and threat detection: Protecting production without slowing developers]() Original publisher: [Read original article]() Author: Ajay Chankramath Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [threat detection](), [Platform Engineering](), [Monitoring](), [Security](), [Containers](), [internal developer platform](), [eBPF](), [Network](), [Processes]() Tags: [blog-post](), [containers](), [developer](), [ebpf](), [firewalls](), [internal-developer-platform](), [monitoring](), [network](), [platform](), [platform-engineering](), [processes](), [security](), [threat-detection]() ### AI overview This article explains how runtime security monitoring protects production workloads from threats that static scans may miss, including privilege escalation, container escapes, unexpected processes, sensitive file access, and suspicious network connections. It presents kernel-level monitoring, including eBPF, as a way to provide continuous protection while embedding security policies into the platform and minimizing developer friction. ### Source excerpt Runtime security monitoring detects zero-days, container escapes, and privilege escalations in production. Discover how eBPF enables 'invisible, always-on' protection for platform engineers ## Backstage TechDocs vs. Port: Modernize your internal documentation DevFeed: [Backstage TechDocs vs. Port: Modernize your internal documentation]() Original publisher: [Read original article]() Author: Roi Talpaz Published: 2026-07-22T11:08:30Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Backstage](), [internal developer portal](), [Developer experience](), [Scalability](), [Architecture & Design]() Tags: [articles](), [backstage](), [blog-post](), [developer-experience](), [documentation](), [idp](), [techdocs]() ### AI overview This article compares Backstage TechDocs with Port as approaches to modernizing internal documentation. It explains how manually maintained documentation becomes stale, causing wasted troubleshooting time, incorrect service setup, workflow disruption, misconfigurations, and security risks. It presents internal developer portals such as Backstage and Port as alternatives that use automated workflows and self-service solutions to reduce reliance on manual updates. ### Source excerpt Compare Backstage TechDocs vs Port to understand documentation workflows, scalability, and developer experience differences. ## Worth Reading: Git Oh-Shit Toolkit DevFeed: [Worth Reading: Git Oh-Shit Toolkit]() Original publisher: [Read original article]() Published: 2026-07-14T05:15:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Git]() Tags: [blog](), [blog-post](), [git](), [worth-reading]() ### AI overview A recommendation for Tony Mattke's Oh-Shit Toolkit, a collection of tools for recovering from mistakes involving Git branches or commit history. ### Source excerpt Tony Mattke published a blog post I wish I'd read 10 years ago. His Oh-Shit Toolkit includes several tools one can use after messing up Git branches or commit history. Definitely worth reading, even if you've been working with Git for ages. ## v19.2.5 Squid released DevFeed: [v19.2.5 Squid released]() Original publisher: [Read original article]() Author: Yuri Weinstein Published: 2026-07-14T00:00:00Z Content type: news Language: en Sources: [Ceph Blog]() Topics: [changelog](), [Amazon S3](), [bug](), [TLS (Transport Layer Security)](), [Authentication](), [Authorization](), [SSL]() Tags: [authentication](), [authorization](), [blog-post](), [bug](), [changelog](), [concurrent](), [configuration](), [en-article](), [en-blog-post](), [object-storage](), [queuing](), [release](), [s3](), [squid](), [ssl](), [tls](), [vector]() ### AI overview Ceph v19.2.5 Squid is the fifth backport release in the Squid series. It fixes issues across MDS, OSD, and RGW, including request queuing faults, rollback and erasure-coding behavior, TLS 1.3 cipher configuration, S3 ACL handling, multisite synchronization, policy evaluation, presigned URL authentication, object tagging, frontend concurrency, and bucket statistics. ### Source excerpt This is the fifth backport release in the Squid series. We recommend all users update to this release. Notable Changes ¶ MDS (Metadata Server) ¶ Fixed a segmentation fault relating to MDSContext completion and request queuing. OSD (Object Storage Daemon) ¶ Rollback & Vector Fixes: Corrected rollback logic for partial write object information (OI) and optimized Erasure Coding (EC) by ensuring Twiddle creates a full-sized vector. RGW (RADOS Gateway) ¶ TLS 1.3 Ciphersuites: Introduced the ssl_ciphersuites configuration option for the Beast front-end to support TLS 1.3 cipher customizations. S3 PutObject ACLs Fix: Fixed a bug where PutObject requests were erroneously rejected under BlockPublicAcls due to an incorrect comparison return value from canned_acl.compare(). Multisite Sync Robustness: Resolved an infinite loop scenario in RGWBucketFullSyncCR when a source bucket was deleted mid-sync by introducing a mechanism to clear stateful data in reused bucket_list_result objects. SNS Policy Evaluation: Updated ListTopics to use the account root ARN for policy evaluation when invoked by a non-root account user, preventing unexpected implicit denies from identity-based policies. Presigned URLs: Fixed an internal server error occurring during the authentication process of presigned URLs. Prerequest Hook: Restructured the order of execution so that the prerequest hook now runs after the authorization process has completed. Object Tagging: Added handling for plain-text object tags during execution of RGWObjTags::decode(). Beast Frontend Stability: Applied a strand executor to the Beast timeout timer to avoid concurrent socket access and potential race conditions. Bucket Statistics: Added a fix for bucket stats execution when the underlying bucket index does not exist. Changelog ¶ [Stretch Mode] mon: restrict changing mon election strategy post stretch mode (pr#65458, Kamoltat Sirivadhna) Check if HTTP\_X\_AMZ\_COPY\_SOURCE header is empty (pr#66028, Suyash Dongre) Fix multifs ## Recover the Ceph Monitor Store Using OSDs DevFeed: [Recover the Ceph Monitor Store Using OSDs]() Original publisher: [Read original article]() Author: Eugen Block, crossposted by Anthony D'Atri Published: 2026-07-04T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [ceph](), [monitor](), [Script](), [Containers](), [log management]() Tags: [blog](), [blog-post](), [ceph](), [containers](), [en-article](), [en-blog-post](), [how-to](), [logging](), [logs](), [mon](), [monitor](), [recovery]() ### AI overview This blog post presents a general procedure for recovering a failed Ceph Monitor store by collecting osdmaps from existing OSDs, with additional considerations for cephadm-managed container deployments. It automates osdmap collection and basic logging while leaving the store rebuild and client authentication steps for careful manual inspection. The procedure applies only to non-encrypted OSDs, and the article emphasizes the importance of backing up dmcrypt/LUKS keys and reviewing host logs. ### Source excerpt Introduction ¶ A few weeks ago I helped a Ceph user to recover his broken cluster (see this thread). Basically, after his Monitors stopped working he re-deployed a new cluster with the same Ceph FSID and attached the existing OSDs to the re-deployed hosts. But it's not that easy to re-activate those OSDs because the new Monitors don't have the old osdmap, hence they don't know anything about the existing OSDs. So how did we fix that? This scenario can be considered a total Monitor store failure. There's a documented procedure in the upstream docs, unfortunately it's written for non-cephadm clusters and doesn't contain many details about subsequent steps. When Ceph daemons run within containers there are more things to consider. So I decided to write this blog post and add some more details to the procedure, targeting mainly clusters managed by cephadm. But the recovery procedure doesn't specifically require cephadm-specific commands, so it can be considered as a general guideline how to recover from a Monitor store loss, just with some extra details about cephadm deployments. This procedure only works for non-encrypted OSDs. If you are using dmcrypt (LUKS) OSDs, make sure you have a backup of the keys, otherwise your data is lost forever! But there is some development, a user in Slack pointed me to this PR which adds a backup mechanism for Monitors, probably available in the upcoming Umbrella release. Note that the PR also contains this statement: Monitor backups complement, but do not replace, the existing Monitor recovery procedures The procedure covered by said docs is already written in script form, so I used that as a template and extended it for cephadm usage and included some very basic logging. It collects the osdmaps from all OSDs and contains the necessary considerations regarding containers. I decided to automate only the osdmap collection, not all required steps of the store rebuild procedure (e. g. Monitor store rebuild, client auth, etc.) because the r ## Reclaim Ceph Capacity Through CephFS Transcoding DevFeed: [Reclaim Ceph Capacity Through CephFS Transcoding]() Original publisher: [Read original article]() Author: Anthony D'Atri Published: 2026-07-01T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [Transcodings](), [Software](), [data]() Tags: [2026](), [4k](), [article](), [blog-post](), [ceph](), [cephfs](), [dram](), [efficiency](), [en-article](), [en-blog-post](), [enterprise](), [enterprise-storage](), [filesystem](), [fujitsu](), [git](), [hardware](), [performance](), [software](), [space](), [storage](), [tentacle]() ### AI overview This article addresses rising storage demands and hardware costs by discussing CephFS capacity efficiency. It describes replicated pools, Erasure Coding, and Fast EC in Ceph Tentacle, while the title identifies CephFS transcoding as the article's focus. ### Source excerpt Data expands to fill available storage (and beyond)! ¶ It used to be that enterprise storage meant 6RU rackmount Fujitsu 2351 Eagles, each holding a mind-boggling 380 MiB of data: enough for a whole company! Today that 380 MiB can't even hold a 4k pickleball video. Enterprises, educational instutitions, and really just about anyone these days demand storage capacities that start on the order of hundreds of tebibytes and rapidly grow to pebibytes. As this article is written in the spring of 2026, the memory market, which includes DRAM, SSDs, and legacy HDDs, has experienced a dramatic escalation of pricing. It is not uncommon to be quoted a price four times what the same hardware cost a year ago, and there are signs that it is going to get worse before it gets better. What's a poor ammonite to do?? Cephers find themselves between the Charybdis of quotes approaching Disaster Area's hypermathematics and the Scylla of hungry users armed with torches and git forks. Git forks, pitchforks. Get it? Sigh. Tough room. Anyway... Short of nuking the site from orbit, how do we make everyone happy, or at worst mildly discontented? Efficiency! CephFS ¶ CephFS is a popular, highly available and scalable software-defined POSIX-style distributed filesystem that can easily store tens of pebibytes of precious data. Or, alternately, cat videos. Ceph deployments often begin small, with replicated pools for perceived performance needs. As the cluster grows to more nodes and more data, it may become feasible and desirable to switch to Erasure Coding (EC) to make more efficient use of raw capacity. An EC pool thus can require substantially less raw storage for a given amount of user data, or store gobs more user data on a given amount of raw capacity This EC overhead table presents efficiency (space amplification) factors for a spectrum of EC profiles. Replicated pools usually maintain three copies of data, so for comparison they manifest an overhead factor of 3.0. EC 4+2 or 6+3 presents a ## Unpacking a database of unknown type DevFeed: [Unpacking a database of unknown type]() Original publisher: [Read original article]() Published: 2026-06-29T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [Database](), [Databases]() Tags: [blog-post](), [database]() ### AI overview A reverse-engineering tutorial explains how to unpack an unknown database file from an unofficial Rutracker dump. It identifies recurring markers in the file, extracts blocks, and uses 7z to unpack them, revealing HTML content from the Rutracker website. ### Source excerpt Unpacking a database of unknown type [Next page]()