Recommend "safe" schedule for use in initializer

[iamvery]

• The bang version removes any existing jobs before scheduling a new one. This has been known to create a race condition on the server. Each delayed job worker loads the app which loads initializers. When this method is called, existing jobs are deleted which effectively prevents any existing recurring job from being invoked by the delayed job worker that is loading.

---

Does that make sense? We're still in the process of verifying this in our app.

[afn]

I would actually go even further and update the README not to recommend putting this in an initializer (which, as you correctly point out, is problematic because it ends up being called from multiple places) and instead set up a rake task as described in the blog post and call this task a single time as part of your deployment process.