On Mon, 14 Jul 2014, PMario wrote:
>> I'm thinking about packaging up Tank as a Docker app to make it easier
>> for people to run their own installations.
>
> I'm not sure, what "run their own installations" mean for you?
>
> Do you want to deliver a "production quality", a "good for private use" or
> a "explore - and throw away" containerised setup?
Good question. I was thinking somewhere between "production quality"
and "good for private use". Perhaps "good for small workgroup or
organization".
"Production quality" is a bit distant at this point, even outside of
docker because the current main site is using an odd hybrid of the
text store, devstore2, and caching store for handling storage and I
don't reckon that's quite good enough for production quality. My
plan has always been to move to postgres but a) I never got around
to it b) what's there is working pretty well so far.
Whatever it is called the idea is that it will be possible for
someone to fill out some configuration files (with things like oauth
secrets, hostname information, paths to attached permanent storage)
and wham, there's your little install.