This is totally doable, my only concerns lie with the Docker version
I want plugins to not be reliant on http-bash-requests (for obvious reasons).
Calling os.Exec from Docker would theoretically work, but this poses new problems
The Dockerfile is mounting the config dir to /taro-files, which only contains the config folder
/taro-bot contains a copy of files in the image
We want to allow the mounted folder to be git pulled to allow easy updates, without fucking up user-level permissions when Docker is run as root
I propose mounting the entire directory taro is built from, and moving config there? Rather than keeping a second mount for config.
You're already intended to build taro yourself, as I don't provide prebuilt images, so keeping a copy of the git repo to allow plugin updates would be entirely optional but required for git pulling plugins.
This is totally doable, my only concerns lie with the Docker version
os.Execfrom Docker would theoretically work, but this poses new problems/taro-files, which only contains the config folder/taro-botcontains a copy of files in the imagegit pulled to allow easy updates, without fucking up user-level permissions when Docker is run as rootI propose mounting the entire directory taro is built from, and moving config there? Rather than keeping a second mount for config. You're already intended to build taro yourself, as I don't provide prebuilt images, so keeping a copy of the git repo to allow plugin updates would be entirely optional but required for git pulling plugins.