thedmsgroup / commit-content Goto Github PK

This is because the registerSchedule method uses the Settings object, which may not exist if this is during an october migration. We just need to make that method fail gracefully if there is not a Settings model/table yet. There's probably a documented way to do this.

Occasionally, a commit might come from another node, and cause a merge to be necessary.

We should make a friendly pull/rebase/merge before a push is made to prevent one node going out of sync with others.

Currently when setting production to use a relative time like "now -1 hour" it works most of the time, but on rare occasion it doesn't get the latest from master. It appears to get stuck at a certain place. An occasional (or always) fetch all should resolve this.