# 使用 Homebrew 安装 doubledown 查看 doubledown 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。 ## 安装 ```sh sudo av install brew:doubledown ``` 其他安装命令: ### macOS - Homebrew (100%): ```sh brew install doubledown ``` 证据: local Homebrew formula metadata ## 软件包事实 - **软件包键:** brew:doubledown - **软件包管理器:** Homebrew - **版本:** 0.0.2 - **来源摘要:** Sync local changes to a remote directory - **主页:** - **仓库:** - **已生成:** 2026-08-03T19:37:03+00:00 ## 可执行文件 - doubledown (别名) - doubledown-fsevents (别名) - doubledown-inotify (别名) ## 安装行为 - Bottle: 不可用 ## 版本和新鲜度 - 页面生成时间: 2026-08-03 - 管理器版本: 0.0.2 ## 项目历史与用法 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. ### 项目历史 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`. ### 采用历史 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. ### 使用方式 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. ### 为什么软件包爱好者会关心 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. ### 时间线 - 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. ### 来源 - - - - ## 安全说明 broad file, network, media, or database tool signal. - **Geiger 风险:** blue / 中 - broad file, network, media, or database tool signal ## Combined YAML source View the package source record on GitHub. [combined/doubledown.yml](https://github.com/mxcl/pkgdb/blob/main/combined/doubledown.yml) ## 来源 - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph