# dry-run Published articles for dry-run. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Treating Pricing Changes Like Code Deploys DevFeed: [Treating Pricing Changes Like Code Deploys]() Original publisher: [Read original article]() Author: Ananda Kanagaraj Sankar Published: 2026-07-22T18:09:48Z Content type: article Language: en Sources: [Thumbtack Engineering - Medium]() Topics: [Deployment](), [DynamoDB](), [Go Language](), [Code review]() Tags: [code-review](), [deployment](), [devops](), [dry-run](), [dynamodb](), [engineering](), [go](), [marketplaces](), [monitor](), [platform-engineering](), [pricing-strategy]() ### AI overview This article explains how Thumbtack handled large pricing changes by comparing them with code deployments. Pricing bids stored in DynamoDB were rewritten in bulk using custom Go scripts, but those scripts lacked built-in resumability, runtime control, and durable records for undoing changes. ### Source excerpt Making large pricing changes safe to run, safe to resume, and safe to undo. Most days, shipping code to production at Thumbtack is a non-event. You merge your change, a deployment pipeline takes it from there and it rolls out while you monitor the rollout. If a deploy stalls, the system already knows which step it stalled on. If it goes wrong, rolling back is a button away. It's the return on years of platform work, so routine now that we mostly forget it's there. Which is the point: Safety is built into the road, not into how carefully each person drives. Changing pricing data never had that platform at Thumbtack. Pricing is how a marketplace like ours sustains itself. It lets us capture a share of the value we help create, and it's something we tune on an ongoing basis rather than set once. We test pricing changes, measure their impact and roll out the ones that work. Mechanically, this runs on an auction. When a customer creates a project on Thumbtack, pros compete for the lead, and what a pro is willing to pay shows up as a bid. Those bids are stored per pro's service offering (a specific offering a pro provides, like house cleaning or landscaping) as bid settings in DynamoDB. Rolling out a pricing change means rewriting those settings in bulk, often a few hundred thousand of them at a time, several times a year. For a long time, each of the pricing rollouts was a custom Go script written for that specific change. The scripts were production grade. They went through code review, ran in staging first, did a dry run before any live write, and were rolled out in stages. That was a reasonable way to work: the changes are infrequent, each one is genuinely different from the last, and a script you can read top to bottom is easy to trust. But what reviews and a good runbook can't give you is the runtime machinery. A script doesn't remember where it was when it died, so it can't safely pick up where it left off. It has no real sense of how hard it's pushing the database ## In Praise of -dry-run DevFeed: [In Praise of -dry-run]() Original publisher: [Read original article]() Author: Henrik Warne Published: 2026-01-31T17:50:03Z Content type: opinion Language: en Sources: [Henrik Warne]() Topics: [Development](), [Testing](), [Database]() Tags: [command](), [configuration](), [development](), [dry-run](), [programming](), [reporting](), [run](), [testing]() ### AI overview The author describes adding a --dry-run option to a reporting application that generates, archives, uploads, and validates reports. The option prints the planned steps without making changes, providing a quick sanity check and helping test report-generation logic safely. ### Source excerpt For the last few months, I have been developing a new reporting application. Early on, I decided to add a -dry-run option to the run command. This turned out to be quite useful - I have used it many times ... Continue reading -> ## Automatizar servidores con Ansible: primeros pasos DevFeed: [Automatizar servidores con Ansible: primeros pasos]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-08T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Ansible](), [Ansible Roles](), [ssh](), [dry-run](), [Git](), [nginx]() Tags: [ansible](), [dry-run](), [git](), [nginx](), [ssh](), [sysadmins](), [variables](), [vault]() ### AI overview A step-by-step introduction to automating server configuration with Ansible. It covers ad-hoc commands, inventories, playbooks, dry runs, roles, group variables, loops, and secrets with ansible-vault. ### Source excerpt Ansible desde cero: comandos ad-hoc, playbooks, roles, variables por grupo, bucles y secretos con ansible-vault, paso a paso. ## Blog: Introducing Falco 0.42.0 DevFeed: [Blog: Introducing Falco 0.42.0]() Original publisher: [Read original article]() Published: 2025-10-22T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [container](), [Processes](), [static linking]() Tags: [bug](), [bug-fixes](), [dry-run](), [falco](), [features](), [memory-leak](), [performance](), [recording](), [release](), [static-linking]() ### AI overview Falco 0.42.0 introduces a capture recording feature that generates .scap files when detection rules trigger, including system-call traces for forensic analysis. The release also includes performance improvements, schema validation, configuration changes, and bug fixes. ### Source excerpt Dear Falco Community, today we are happy to announce the release of Falco 0.42.0! This release brings exciting new capabilities, including the capture feature, significant performance improvements, and important bug fixes that enhance Falco's capabilities. During this release cycle, we merged: 52 PRs on Falco, including 23 release note-worthy changes 110 PRs on Falco libs, including 47 release note-worthy changes 102 PRs on Falco drivers, including 29 release note-worthy changes We upgraded libs to version 0.22.1 and drivers to v9.0.0+driver. Thank you to our maintainers and contributors. This would not have been possible without your support and dedication! To learn everything about the changes, read on! What's new? TL;DR Key features: Capture recording feature; Drop enter initiative for performance; Plugin event schema validation; Thread table auto-purging configuration; Static fields; Key fixes: Fix thread table memory leak when parsing vfork (or equivalent clone/clone3 with CLONE_VFORK) exit from the caller process; Enable handling of multiple actions configured with syscall_event_drops.actions; Disable dry-run restarts when Falco runs with config-watching disabled; Fix abseil-cpp for Alpine build; Fix detection sandbox containers for CRI and containerd runtimes (container plugin); Stability improvements for container plugin and static linking of libgcc/libstdc++ for legacy compatibility; This release also comes with breaking changes that you should be aware of before upgrading. Major features and improvements The 0.42.0 release contains a new capture feature and significant performance improvements. Here is a list of the key new capabilities. Capture recording feature Falco 0.42.0 introduces the new capture recording feature, now available at sandbox maturity. This capability allows Falco to generate .scap files whenever a detection rule is triggered automatically. Each capture contains a detailed trace of system calls around the event, providing forensic-level ## Remote Deployments with nixos-rebuild DevFeed: [Remote Deployments with nixos-rebuild]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2023-08-10T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Deployment](), [systems](), [configuration]() Tags: [configuration](), [deploy](), [deployments](), [dry-run](), [systems]() ### AI overview This tutorial explains the locality axis of nixos-rebuild, covering remote builds and deployments across a local machine, a build host, and a target host. It describes selecting the NixOS configuration, deploying to another host, and copying and activating the resulting system configuration. ### Source excerpt Explore how nixos-rebuild's remote capabilities simplify deployment across machines. Learn the efficient steps for seamless remote builds and deployments! ## Using nixos-rebuild for NixOS Configuration, Upgrades, Rollbacks, and Testing DevFeed: [Using nixos-rebuild for NixOS Configuration, Upgrades, Rollbacks, and Testing]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2023-07-31T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [configuration](), [Deployment](), [upgrade](), [dry-run]() Tags: [configuration](), [deployment](), [dry-run](), [tooling](), [upgrade]() ### AI overview This tutorial explains nixos-rebuild, the standard tool for changing an installed NixOS system. It covers configuration changes, input updates, upgrades, rollbacks, dry runs, virtual-machine testing, local rebuilds, and remote deployment or building. ### Source excerpt Discover the power of nixos-rebuild for seamless system configuration, upgrades, and rollbacks with just a few commands. Explore its versatile capabilities! ## Transfer many large files from Android DevFeed: [Transfer many large files from Android]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2022-12-17T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [adb](), [Command-line interface](), [Shell]() Tags: [adb](), [android](), [backup](), [blogs](), [disk-space](), [dry-run](), [files](), [large-files](), [storage]() ### AI overview A tutorial on using ADB to transfer many large files from an Android phone when Android File Transfer is unreliable or disk space is limited. It explains pulling files in batches and safely deleting only files that were synchronized. ### Source excerpt Trying to get a large number of files from your Android phone, but Android File Transfer freezing up? Here's what I learned trying to pull ~170 Gb from my Pixel phone. ## Improve your Android build times DevFeed: [Improve your Android build times]() Original publisher: [Read original article]() Author: Manideep Polireddi Published: 2016-04-05T20:10:00Z Content type: tutorial Language: en Sources: [@okmanideep]() Topics: [Gradle](), [Android](), [build times](), [build performance](), [modules]() Tags: [android](), [android-studio](), [build](), [build-performance](), [build-times](), [command-line](), [dry-run](), [gradle](), [modules]() ### AI overview This tutorial presents ways to reduce Android and Gradle build times, including using a Gradle daemon, upgrading Gradle, using JDK 8, enabling parallel execution for standalone modules, and avoiding dynamic dependencies and expensive repository computations. ### Source excerpt Simple things you can do to improve your gradle/android build time a lot ## Recovering Lost Post Data DevFeed: [Recovering Lost Post Data]() Original publisher: [Read original article]() Author: Jay (noreply@blogger.com) Published: 2013-05-07T12:00:00Z Content type: tutorial Language: en Sources: [Jay Fields]() Topics: [Chrome](), [developer tooling](), [dry-run]() Tags: [chrome](), [devtools](), [dry-run](), [error](), [logging](), [network]() ### AI overview A practical guide to recovering form data after a session-expired error by using Chrome DevTools. It explains how to inspect the Network tab, find the POST request, allow a repost if prompted, and copy the contents of Form Data. ### Source excerpt I recently typed out a long, thoughtful response in a textarea. I clicked submit, like I've done millions of times, and I got the dreaded "session expired" error message. This happens very, very rarely, but it's devastating when it does. Creating long & thoughtful responses isn't something that comes naturally for me. I crossed my fingers and clicked back. No luck, web 2.0 dynamically created text boxes ensured Chrome had no chance to preserve my editing state. My first reaction was: I guess I'm not responding after all. Then it occurred to me, DevTools must have my data somewhere, right? Lucky for me, the answer was yes. There might be easier ways, this is what worked for me: open DevTools go to the "Network" tab. look for the row with the method POST. If you don't see a POST row, try refreshing the page. With any luck you'll get a repost confirmation dialog, giving you some hope that your data is still around. (You'll want to allow the data repost) click on the POST row, and scroll down till you see "Form Data". If you've gotten this far, hopefully you'll find your data in clear text and able to be copied. The examples from this post are from following the instructions above and logging in to twitter.com. If you've ever lost post data in the past, you may want to give these directions a dry-run now. © Jay Fields - www.jayfields.com