Running Unisync in the Background

Once you're confident that unisync is working the way you want it to, you can run it to the background just by adding -start to the command you run. For example, instead of:

unisync myproject

.. you would instead run:

unisync -start myproject

You'll see it run long enough to make sure the connection is working fine, then detach itself and go into the background. It will automatically try to reconnect if the connection drops.

If you want to check on how it's doing in the background, you can look at its log file. Every instance will create one by default, whether it's running in the background or not, unless you disabled it with log= (see the Configuration documentation for more). By default, you'll find the log file in ~/.unisync/myproject.conf.log.

List running background instances

unisync -status

Stop a running instance

unisync -stop myproject

Stop all running instances

unisync -stopall

Limitation for DirectTLS servers

Currently the -start flag does not work with the -server flag, which is used to run a DirectTLS server. If you need to continuously run a DirectTLS server in the background, you should use tmux or systemd. This limitation will be removed in a future release.