macOS
Homebrewverifiziert · 100%
brew install doubledownlocal Homebrew formula metadata
brew
doubledown mit Homebrew installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für doubledown in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
Sync local changes to a remote directory
Projektlinks
Befehle und Aliase
- doubledown
- doubledown-fsevents
- doubledown-inotify
Verlauf
Projektgeschichte und Nutzung
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.
Projektgeschichte
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`.
Adoptionsgeschichte
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.
Wie es verwendet wird
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.
Warum Paket-Nerds sich dafür interessieren
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.
Zeitleiste
- 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.
Quellen
Sicherheitslage
Risikostufe: blue
broad file, network, media, or database tool signal.
Risikoklassifikator
blue Risiko · mittel Konfidenz · tool
Warum
- broad file, network, media, or database tool signal
Signale
- text:sync
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
doubledown | cli | globales Executable | |
doubledown-fsevents | cli | globales Executable | |
doubledown-inotify | cli | globales Executable |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-07-08
Manager-Version0.0.2
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.0.2
https://github.com/devstructure/doubledown
- InfoNo package-manager update timestamp was available.niedrig Konfidenz
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:doubledown |
|---|---|
| Version | 0.0.2 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/doubledown |
| Homepage | https://github.com/devstructure/doubledown |
| Repository | https://github.com/devstructure/doubledown |
| Upstream-Dokumentation | https://github.com/devstructure/doubledown#readme |
| Lizenz | BSD-2-Clause |
| Quellarchiv | https://github.com/devstructure/doubledown/archive/refs/tags/v0.0.2.tar.gz |
| Bottle | verfügbar (auf all) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | doubledown |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- 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