Supply custom plugins as startup

[peterabbott]

It would nice if plugins could be provided as part of the startup instead of copying them after startup.

I can see there is an add-ons directory but that appears to be used for configuring things like the underlying database setup.

Because the folders get created after first startup it makes it difficult to mount a folder. The only options it to extend and use the COPY/RUN commands to put the files in place and then change ownership of the directory tree.

Is there something I have missed? Otherwise I will work on an update to the Dockerfile

[arvindsv]

Could be related to #12? Yes, it would be nice to be able to have a proper data container strategy. Does it make sense to provide a data container image, with the right structure and no files (for the first time), so that someone can use --volumes-from from it, and have the go-server image work with that?

Doesn't just mounting /var/lib/go-server/plugins/external work? Permission issues? Something else? I haven't checked. But, I think having a way to provide custom plugins at startup is a valid use case.