Automic VaultAutomic Vault

brew

Install doubledown with Homebrew

Sync local changes to a remote directory. Version 0.0.2 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install doubledown

local Homebrew formula metadata

overview

Package summary

Sync local changes to a remote directory

Commands and aliases

  • doubledown
  • doubledown-fsevents
  • doubledown-inotify

history

Project history and usage

doubledown is a DevStructure command-line tool for syncing local changes to a remote directory over SSH and rsync, then watching the local directory for further changes. Its README presents it as a helper for users who wanted to edit locally in TextMate or another IDE while deploying changes to a remote server.

Project history

The GitHub repository was created in August 2010 and the README credits Richard Crowley as author. The tool belongs to the pre-container, pre-cloud-IDE deployment era when many developers edited files locally but tested or ran them on a remote Unix host.

Its implementation model is intentionally built from classic Unix pieces: ssh-agent for authentication, SSH keys, rsync for initial bidirectional synchronization, and platform file watchers through `doubledown-fsevents` and `doubledown-inotify`.

Adoption history

The repository has tags for early releases such as v0.0.1 and v0.0.2, with GitHub activity concentrated between 2010 and 2013. Homebrew packaging keeps the command discoverable, but the project appears historically useful rather than broadly active today.

doubledown's adoption story is tied to DevStructure users and local-editor remote-development habits before tools like VS Code Remote, Mutagen, Syncthing, and container-native development environments became common.

How it is used

The documented command shape is `doubledown [-i identity] local [user@]server:remote`. It starts or uses an ssh-agent, requires SSH key authentication, pulls remote files that do not exist locally, uploads local changes, and then hands off to a filesystem watcher.

Because it repeatedly connects to the server, the README explicitly requires SSH key pairs rather than password authentication. That makes it closer to a developer loop tool than a one-shot file transfer command.

Why package nerds care

doubledown is a neat package-manager fossil: a small wrapper around SSH, rsync, and file watching that captures a specific remote-development workflow from the early 2010s.

Its significance is mainly historical. It shows how much developer tooling used to be composed from narrow Unix commands before integrated remote IDEs and always-on sync daemons absorbed that workflow.

Timeline

  • 2010: Public GitHub repository created.
  • 2010: Early v0.0.x tags appear in the repository.
  • 2013: Last recorded repository push date in the GitHub API.
  • 2026: Homebrew still carries a doubledown formula.

Related projects

  • rsync and SSH are the core transport and synchronization tools that doubledown wraps.
  • doubledown-fsevents and doubledown-inotify handle platform-specific file watching.
  • Mutagen, Syncthing, Unison, and editor-native remote development tools cover adjacent synchronization workflows today.

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

  • broad file, network, media, or database tool signal

Signals

  • text:sync

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
doubledowncliglobal executable
doubledown-fseventscliglobal executable
doubledown-inotifycliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.0.2
manager updated
local dataok
upstreamcurrent
latest detectedv0.0.2

https://github.com/devstructure/doubledown

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:doubledown
Version0.0.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/doubledown
Homepagehttps://github.com/devstructure/doubledown
Repositoryhttps://github.com/devstructure/doubledown
Upstream docshttps://github.com/devstructure/doubledown#readme
LicenseBSD-2-Clause
Source archivehttps://github.com/devstructure/doubledown/archive/refs/tags/v0.0.2.tar.gz
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedoubledown
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment