Install & Remove plugins through a command about avaire

[Macleykun]

Yeah, my level of thinking isn't even close as high as you can think X3.

Dig the idea to set it default on false and to use a nice table to keep track of everything.

And yes the re-download feature should only work if someone used the plugin command! It'll probably create issues if it would just be added manually (like for example when someone is testing out it's own made plugin).

Really dig the idea's you've thrown into this feature/issue! It would be insanely easy to host AvaIre on Heroku, withoud any limitations (aside of uptime obviously).

[Macleykun]

🎉 #132

[Macleykun]

If this get's added, would it be possible that when say:

1. User adds plugin using the command.
2. Plugin get's added
3. When the bot restarts, it checks if the plugin is present, if not, it adds it again (downloading).

That way, we could support plugins "natively" on Heroku aswell. Withoud the user needing to edit any files!

[Senither]

It could be done by creating an index of plugins that should exist as the bot starts up so it can re-download them if they're not present, however, it would have to be an option that the user has to turn on(some config option, or environment variable for Heroku), otherwise it might just create more confusion than anything else if people not using Heroku deletes a plugin manually and then the bot just re-download it again.

[Macleykun]

True, i suggest the idea of using an enviroment variable.

Maybe something like persistant plugin? Or plugin-check?

[Senither]

Doesn't really matter what the environment variable would be called, it would just be a boolean flag anyways, so by default, the option is false but can be turned on with the environment variable, when enabled, plugins installed via the ;plugin command would be indexed in some database table, allowing the bot to keep track of what plugins should exist, if they don't exist it can use the information in the database to re-loaded them.

The re-download feature would only work for plugins that are actually installed via the plugins command since that system uses the plugin index created for Ava, which points plugin projects to their respective GitHub/BitBucket/GitLab repositories where it can download the releases of the plugin.