3. password-free login (public key authentication) from client to
server. [Here](http://www.debian-administration.org/articles/152) is a
-good page on how to set it up.
+good page on how to set it up (*).
4. a reasonably fast connection. (This isn't really *necessary*, but if
your connection is too slow, this won't be very pleasant to use, and
certainly won't seem transparent.)
+(*) If you don't want / cannot use password-free login,
+[[This|remoteusage/124]] page provides yet another alternative.
+
## Configure `ssh` on the client computer ##
Add this to your `~/.ssh/config`:
HostName example.com
User remoteuser
ControlMaster auto
- ControlPath /home/user/.ssh/%h_%p_%r
+ ControlPath ~/.ssh/master-%h@%p:%r
ControlPersist 15m
- IdentityFile /home/user/.ssh/example.com.id_rsa
+ IdentityFile ~/.ssh/example.com.id_rsa
Replace `example.com` with your server. Replace `remoteuser` with the
-username on the server. Replace `/home/user` with your home directory.
+username on the server.
The `Control*` options keep the connection open in the background to not
require authentication every time. The `ControlPersist` option defines
printf -v ARGS "%q " "$@"
exec ssh notmuch notmuch ${ARGS}
+and give it execute permissons: `chmod +x remote-notmuch.sh`
+
Now you can run `remote-notmuch.sh new`, or other notmuch commands. You
can call the script anything you like. (You could also call it `notmuch`
or symlink `~/bin/notmuch` to it for transparent usage.)
to list them here. And, of course, if you improve on any of these
approaches, please do edit this page and let people know!
-If you have issues, you may want to try the [[old remote usage
-instructions|remoteusage-old]].
+If you have issues, you may want to try the
+[[old remote usage instructions|remoteusage/old]] or
+[[yet another alternative|remoteusage/124]].