# zero Published articles for zero. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Announcing automated, zero-downtime migrations to Temporal Cloud DevFeed: [Announcing automated, zero-downtime migrations to Temporal Cloud]() Original publisher: [Read original article]() Author: Nikitha Suryadevara Published: 2025-03-04T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [migration](), [Cloud](), [Self-hosted](), [API](), [proxy](), [Replication](), [Security]() Tags: [api](), [automated](), [cloud](), [migrate](), [migrations](), [product-news](), [proxy](), [replication](), [security](), [self-hosted](), [zero]() ### AI overview Temporal announces pre-release migration tooling for moving self-hosted Temporal instances to Temporal Cloud. It is designed to automate the migration while keeping long-running workflows running and avoiding application-code changes. ### Source excerpt Easily migrate from self-hosted Temporal to Temporal Cloud with zero downtime. Fully automated, seamless, and built to minimize effort. ## Atomic Deployments Without Tears DevFeed: [Atomic Deployments Without Tears]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-06-30T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [CI/CD](), [Deployment](), [Git](), [Content Management System](), [Development]() Tags: [amazon-s3](), [atomic](), [automatically](), [changes](), [continuous](), [continuous-integration](), [deploy](), [deployments](), [downtime](), [git](), [how-to](), [insights](), [integration](), [learn](), [safely](), [tools](), [using](), [website](), [zero]() ### AI overview This tutorial explains how to use Continuous Integration tools to perform atomic, zero-downtime deployments for Craft CMS websites. It covers a workflow based on local development, a cloud Git repository, and automated deployment to production or staging servers. ### Source excerpt Learn how to use atomic deployments to automatically and safely deploy changes to your website with zero downtime using Continuous Integration (CI) tools ## Project PITA: Build a Mini Mass Deauther Using Bettercap and a Raspberry Pi Zero W DevFeed: [Project PITA: Build a Mini Mass Deauther Using Bettercap and a Raspberry Pi Zero W]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2018-07-28T17:01:56Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Raspberry Pi](), [Linux](), [Network](), [configuration](), [ssh](), [Bluetooth](), [clients](), [file]() Tags: [bettercap](), [ble](), [bluetooth](), [btnap](), [cybersecurity](), [deauth](), [handshake-capture](), [kali](), [linux](), [monitor-mode](), [packet-injection](), [pi](), [portable-hacking](), [project](), [raspberry](), [raspberry-pi](), [rpi](), [rpi-zero-w](), [rpi0w](), [wifi](), [wireless-security](), [wpa2](), [writeup](), [zero]() ### AI overview A writeup showing how to build a pocket-sized WiFi deauthenticator with a Raspberry Pi Zero W, Kali Linux, Nexmon drivers, and bettercap. It covers WiFi scanning, deauthentication packets, WPA2 handshake capture, initial SSH and WiFi configuration, and Bluetooth access. ### Source excerpt A few days ago I started playing with some idea I had from a few weeks already, using a Raspberry Pi Zero W to make a mini WiFi deauthenticator: something in my pocket that periodically jumps on all the channels in the WiFi spectrum, collects information about the nearby access points and their connected clients and then sends a deauthentication packet to each one of them, resulting in some sort of WiFi jammer on the 802.11 level. As an interesting "side effect" of this jammer (the initial intent was purely for the lulz) is that the more it deauths, the higher the changes to also sniff WPA2 handshakes. Thanks to the awesome work of the Kali and Nexmon communities in packaging the nexmon drivers and utilities and to the recent changes we released in bettercap, this was very easy to setup and to script and given the interest the tweet had I thought to share this writeup :) This awesome case has been designed by @elkentaro and can be found on [his Thingverse page](https://www.thingiverse.com/thing:3018480). ## Live restarts of a supervised unicorn process DevFeed: [Live restarts of a supervised unicorn process]() Original publisher: [Read original article]() Author: Sam Saffron Published: 2013-11-13T04:59:56Z Content type: tutorial Language: en Sources: [Sam Saffron]() Topics: [Scripting, bash](), [Script](), [Rails](), [Processes](), [HTTP]() Tags: [bash](), [docker](), [downtime](), [rails](), [script](), [uptime](), [zero]() ### AI overview The article describes using a Bash script as a stable-pid proxy and mini-supervisor for Unicorn to coordinate live restarts under supervisors such as runit. It also presents a throttled HTTP request script for measuring downtime during restarts and reports zero downtime with the proposed method. ### Source excerpt We have all seen this dreaded screen before. In the Rails case this usually happens during application restarts. While Discourse is rapidly evolving we are heavily encouraging users to upgrade frequently, even weekly. If your site is regularly erroring out, users very quickly lose confidence. In the ideal case you want zero downtime deploys. This feature heavily encourages users to deploy more rapidly. Unicorn has built-in support for live restarts, however getting this to play well with a supervisor like say runit is not easy. Underlying pids are changing and stuff gets complicated fast. To tackle this I decided to create a simple bash script that acts as a mini-supervisor for unicorn. However, before any of this I needed some sane way of measuring how well I did. ###Measuring uptime during a live restart Traditionally you would use apache bench for quick and dirty testing, however it did not fare well for me. Unfortunately ab has no way of "throttling" the amount of requests it sends out. To measure uptime we need to perform a request to the site every N milliseconds. I ended up knocking up a quick and dirty apache bench clone that allows me to trickle through requests: require "optparse" require "uri" require "net/http" duration = 10 per_second = 10 opts = OptionParser.new do |opts| opts.banner = "Usage: bench_web [options] url" opts.on("-t", "--time TIME", OptionParser::DecimalInteger, "Duration to run the test in seconds (default 10)") do |t| duration = t end opts.on("-p", "--per-second REQUESTS", OptionParser::DecimalInteger, "Max number of requests per second (default 10)") do |t| per_second = t.to_f end end opts.parse! if ARGV.length != 1 puts opts.banner puts exit(1) end uri = begin URI(ARGV[0]) rescue puts opt.banner puts puts "Invalid URL" puts exit(1) end GC.disable finish_time = Time.now + duration results = [] while (start=Time.now) < finish_time res = Net::HTTP.get_response(uri) req_duration = Time.now - start results << {duration: req_duration, code: ## Online upgrades in Go DevFeed: [Online upgrades in Go]() Original publisher: [Read original article]() Author: Graham King Published: 2013-07-21T04:40:55Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Go Language](), [servers](), [Unix](), [Process]() Tags: [code](), [downtime](), [go](), [guide](), [kernel](), [server](), [software](), [tcp](), [unix](), [upgrades](), [zero]() ### AI overview A guide to upgrading a Go server without dropping long-running connections. It explains file-descriptor inheritance and passing descriptors over UNIX domain sockets, with an example that transfers connections to a new process during an upgrade. ### Source excerpt Upgrade your server without dropping connections: A guide to zero downtime upgrades.