git-annex-remotedaemon(1)

✨ git-annex-remotedaemon(1) ✨

okay bestie, so this one's from the General Commands Manual and it's literally called git-annex-remotedaemon(1) — say that five times fast 💅 it's the page about keeping the vibes persistent with your remotes.

---

🦋 NAME 🦋

git-annex-remotedaemon — persistent communication with remotes

---

🌸 SYNOPSIS 🌸

git annex remotedaemon

---

💖 DESCRIPTION 💖

The remotedaemon is the one who keeps the group chat open. It provides persistent communication with remotes. no ghosting, no dropped calls 💅

Several types of remotes are supported, and each one has its own little moment:

• ssh remotes — the remotedaemon tries to maintain a connection to the remote git repository, and it uses git-annex-shell notifychanges to detect when the remote git repository has changed, and then it fetches changes from it. For this to work, the git remote must have git-annex-shell(1) installed, with notifychanges support. The first version of git-annex-shell that supports it is 5.20140405. (yes, a whole era ago, she's vintage ✨)
• tor-annex remotes — the remotedaemon runs a tor hidden service, accepting connections from other nodes and serving up the contents of the repository. This is only done if you first run git annex enable-tor. Use git annex p2p to configure access to tor-annex remotes. 🧚
• p2p-annex remotes — the remotedaemon runs a command git-annex-p2p-<netname> to get a socket file, listens to the socket file for connections from other peers, and serves up the contents of the repository. This is only done if you first run git-annex p2p --enable <netname>. iconic behavior tbh 🫶

heads up queen 👑 — when remote.<name>.annex-pull is set to false, the remotedaemon will avoid fetching changes from that remote. she respects the boundary, periodt.

---

🎀 OPTIONS 🎀

• --foreground — Don't fork to the background, and communicate on stdin/stdout using a simple textual protocol. The assistant runs the remotedaemon this way.

Commands in the protocol include LOSTNET, which tells the remotedaemon that the network connection has been lost, and causes it to stop any TCP connections. That can be followed by RESUME when the network connection comes back up. it's giving "brb wifi died" then "ok I'm back" 😭

Also the git-annex-common-options(1) can be used. yes bestie, more flags, go off 💅

---

🌈 SEE ALSO 🌈

• git-annex(1)
• git-annex-assistant(1)
• git-annex-enable-tor(1)
• git-annex-p2p(1)

---

💜 AUTHOR 💜

Joey Hess <id@joeyh.name> — the main character who wrote all this, we stan 🫶

---

and that's the whole page babes, tysm for reading 💖 this was git-annex-remotedaemon(1), straight out of the General Commands Manual — go forth and daemon responsibly, mwah 🎀✨