Since merging #54, we now have a systemd service file that manages running the crawler over time, including automatic restarting. The Ansible logic does not ensure that the crawler service is started, however—developers must still start crawls manually.
Let's add a service task to the crawler provisioning logic to ensure the crawler gets started and enabled (meaning it will start after a reboot as well).
Since merging #54, we now have a systemd service file that manages running the crawler over time, including automatic restarting. The Ansible logic does not ensure that the crawler service is started, however—developers must still start crawls manually.
Let's add a service task to the crawler provisioning logic to ensure the crawler gets started and enabled (meaning it will start after a reboot as well).