Open johnk- opened 10 years ago
Should each command live in its own repo? Might be simpler.
That is one option. Another might be to have a list-of-active-commands file in the same location as the commands. That way we could also easily disable a command by updating the list.
A good reason for separate commands might be that the bot could respond to commit notifications (via an email check on a dedicated address, for example) and wouldn't need to do anything other than download that specific command. If they were all in one place, it'd be more complicated to react to commit notifications (I think). To get around that I supposed you could just pull down all active commands whether they had changed or not, but that seems a waste. An active command list could be useful, in any case.
load-thru isn't around any more, but I was thinking of something similar. Maybe the command list could include a last updated date/time or checksum
Github provides a plain http way of getting to your repository. Update command loadingy so it automatically pick up changes from github.