plerdwatcher - Daemon that automatically updates a Plerd-based blog when needed


In /path/to/plerd/conf/plerd.conf:

 base_uri: path: /home/me/Dropbox/plerd title:
 My Lovely Blog

And then, on the command line, while in the top-level plerd directory:

 bin/plerdwatcher start


This script launches a simple daemon that monitors a Plerd blog's directory of Markdown-based source documents for changes. When it sees changes, it will direct Plerd to publish or republish files as needed.

It also supports options to send and receive webmentions, as described in "OPTIONS", below.

plerdwatcher runs via App::Daemon, and accepts all the command-line arguments documented there.

It stores its logs in a directory called log and other run-time files in a run directory, both of which it expects to find as siblings of its own parent directory (usually bin).

For instructions on installing and using Plerd, please see the README file that should have accompanied this distribution. It is also available online at



 bin/plerdall --config=/path/to/plerd.conf

Specify the location of a valid Plerd config file.

If not specified here, then this program will seek a config file in these locations, and in this order:

  • plerd.conf, in the current working directory

  • conf/plerd.conf, in the current working directory

  • .plerd, in your home directory

Consult the config file generated by plerdall --init to learn more about the config file format.


All of these Webmention-related options are experimental.


 bin/plerdwatcher --send-webmentions start

Newly created or updated posts will also attempt to send webmentions to any URLs they link to.


 bin/plerdwatcher --receive-webmentions=4000 start

 bin/plerdwatcher --receive-webmentions=4000 --ssl-cert=/path/to/cert.pem --ssl-key=/path/to/key.pem start

Launches a webserver that listens on the specified TCP port. This will allow plerdwatcher to receive webmentions.

If you want to use an SSL cert/key pair with this (so that plerdwatcher will listen for webmentions via HTTPS, rather than HTTP) add --ssl-cert and --ssl-key options as well.



Jason McIntosh <>