rename *-daemon apps to be *-backend

Squashed commit of the following:

commit 39b438aa4b
Author: Oliver Gorwits <oliver@cpan.org>
Date:   Sat May 6 16:40:11 2017 +0100

    add release notes

commit ca4ea90d35
Author: Oliver Gorwits <oliver@cpan.org>
Date:   Sat May 6 16:32:06 2017 +0100

    update distmeta

commit 4e35b904b0
Author: Oliver Gorwits <oliver@cpan.org>
Date:   Sat May 6 16:30:22 2017 +0100

    rename files from Daemon to Backend

commit 86a605ba68
Author: Oliver Gorwits <oliver@cpan.org>
Date:   Sat May 6 16:26:43 2017 +0100

    rename daemon to backend in code

commit ffe8fc180f
Author: Oliver Gorwits <oliver@cpan.org>
Date:   Sat May 6 16:15:57 2017 +0100

    add daemon files which exec to backend equivalents

commit 53e041594e
Author: Oliver Gorwits <oliver@cpan.org>
Date:   Sat May 6 15:32:49 2017 +0100

    rename netdisco-daemon to netdisco-backend

lib/App/Netdisco/Manual/Deployment.pod

@@ -7,7 +7,7 @@ App::Netdisco::Manual::Deployment - Tips and Tricks for Deployment
 The Netdisco applications will generate RC scripts suitable for Linux systems:
 
  bin/netdisco-web get_init_file
- bin/netdisco-daemon get_init_file
+ bin/netdisco-backend get_init_file
 
 On C<systemd>-based systems please see L<our systemd
 guide|App::Netdisco::Manual::Systemd>.

lib/App/Netdisco/Manual/Developing.pod

@@ -51,14 +51,14 @@ directory
 You might also want to set C<check_userlog> to C<false> in your config to
 quieten some of the web client callbacks.
 
-For the daemon, it's very similar:
+For the backend daemon, it's very similar:
 
- DBIC_TRACE=1 ~/bin/localenv bin/netdisco-daemon-fg
+ DBIC_TRACE=1 ~/bin/localenv bin/netdisco-backend-fg
 
 You can point at a different database without editing C<deployment.yml>:
 
  NETDISCO_DBNAME=testdb DBIC_TRACE=1 ~/bin/localenv plackup -R share,lib -p 5001 bin/netdisco-web-fg
- NETDISCO_DBNAME=testdb DBIC_TRACE=1 ~/bin/localenv bin/netdisco-daemon-fg
+ NETDISCO_DBNAME=testdb DBIC_TRACE=1 ~/bin/localenv bin/netdisco-backend-fg
 
 It's recommended to delete the "C<~/perl5/lib/perl5/App/Netdisco>"
 directory to avoid accidentally picking up old Netdisco code. For working on
@@ -398,7 +398,7 @@ database connection management features mentioned above.
 
 The job daemon is backwards compatible with the old Netdisco database job
 requests table. All code for the job daemon lives under the
-L<App::Netdisco::Daemon> namespace and like the rest of Netdisco is broken
+L<App::Netdisco::Backend> namespace and like the rest of Netdisco is broken
 down into manageable chunks.
 
 =head2 Running the Job Daemon
@@ -407,10 +407,10 @@ Like the web application, the job daemon is fully self contained and runs via
 two simple scripts shipped with the distribution - one for foreground and one
 for background execution (see the user docs for instructions).
 
-The C<netdisco-daemon> script uses L<Daemon::Control> to daemonize so you can
+The C<netdisco-backend> script uses L<Daemon::Control> to daemonize so you can
 fire-and-forget the Netdisco job daemon without much trouble at all. This
-script in turn calls C<netdisco-daemon-fg> which is the real application, that
-runs in the foreground if called on its own.
+script in turn calls C<netdisco-backend-fg> which is the real application,
+that runs in the foreground if called on its own.
 
 =head2 Daemon Engineering
 

lib/App/Netdisco/Manual/ReleaseNotes.pod

@@ -35,6 +35,22 @@ deploy script for App::Netdisco will make some schema changes to the database,
 but they are backwards compatible.
 
 =back
+=head1 2.036000
+
+=head2 Health Advice
+
+In this release the apps C<netdisco-daemon> and C<netdisco-daemon-fg> have
+been renamed to C<netdisco-backend> and C<netdisco-backend-fg> respectively.
+
+This better reflects the function of the two programs. If you still have
+scripts using C<netdisco-daemon> or C<netdisco-daemon-fg> commands, they
+should continue to work, as these apps still exist and simply exec() to the
+new scripts on start.
+
+However, it would be best if you replace any custom management config to
+point to the new app names, going forward. Remember to do this on upgrade:
+
+ ln -s ~/perl5/bin/{localenv,netdisco-*} ~/bin/
 
 =head1 2.035007
 

lib/App/Netdisco/Manual/Systemd.pod

@@ -10,21 +10,21 @@ instructions apply to your local installation and use at your own risk.
 
 =head1 Files
 
-=head2 C<< /etc/systemd/system/netdisco-daemon.service >>
+=head2 C<< /etc/systemd/system/netdisco-backend.service >>
 
 This should be set mode 644 and owned by user and group C<root>.
 
   [Unit]
-  Description=Netdisco Daemon Service
-  AssertFileIsExecutable=/home/netdisco/bin/netdisco-daemon
+  Description=Netdisco Backend Service
+  AssertFileIsExecutable=/home/netdisco/bin/netdisco-backend
   After=syslog.target network-online.target
   
   [Service]
   Type=forking
   User=netdisco
   Group=netdisco
-  ExecStart=/home/netdisco/bin/netdisco-daemon start
-  ExecStop=/home/netdisco/bin/netdisco-daemon stop
+  ExecStart=/home/netdisco/bin/netdisco-backend start
+  ExecStop=/home/netdisco/bin/netdisco-backend stop
   Restart=on-failure
   RestartSec=60
   
@@ -38,7 +38,7 @@ This should be set mode 644 and owned by user and group C<root>.
   [Unit]
   Description=Netdisco Web Service
   AssertFileIsExecutable=/home/netdisco/bin/netdisco-web
-  After=syslog.target network-online.target netdisco-daemon.service
+  After=syslog.target network-online.target netdisco-backend.service
   
   [Service]
   Type=forking
@@ -56,15 +56,15 @@ This should be set mode 644 and owned by user and group C<root>.
 
 To enable Netdisco in systemd:
 
- systemctl enable netdisco-daemon.service
+ systemctl enable netdisco-backend.service
  systemctl enable netdisco-web.service
 
 To start Netdisco:
 
- systemctl start netdisco-daemon.service
+ systemctl start netdisco-backend.service
  systemctl start netdisco-web.service
 
-May also need to run C<systemctl daemon-reload> depending on the order you do
-these steps.
+May also need to run C<systemctl netdisco-backend reload> depending on the
+order you do these steps.
 
 =cut