Step one: DB Configuration

Add sqlite3 gem so that the daemon can connect to the db used by the
demo rails app.
Step Two: Peg Rufus-Schedule to a 2.X version

Left like this `bundle install` will install a 3.0 version of Rufus
Scheduler and that will cause problems.
Step Three: Bundle Install

Get your gems installed.
Step Four: Create a scheduled call to a rake task.

The rake task is where the real work is done. You want the code in
libexec/customer_onboarding-daemon.rb to be as light as possible, since
it's what will be growing (or not) the memory footprint of your daemon.

Calling rake is perfect because it will run in a separate process and
that process will die once the work is complete. So you don't have to
worry about that memory.
Step Five:

Write the rake task that you're calling from
libexec/customer_onboarding-daemon.rb.

Since this is a demonstration, this task doesn't actually do anything.
Real work is left as an exercise for the reader.
Step Six: Logging

A very simple demonstration of the DaemonKit logger.