Right now I just have the history hook running on production too. This is likely bad, but due to ease of deploy, I just did that for now. A better scenario is a history daemon that runs through and executes things it sees. This can be implemented via the cron, and run as much as possible
Right now I just have the history hook running on production too. This is likely bad, but due to ease of deploy, I just did that for now. A better scenario is a history daemon that runs through and executes things it sees. This can be implemented via the cron, and run as much as possible