COmanage Developers List

[Tom Zeller <>]

Hi Scott - responses below --Tom

> How specifically will that image differ from the current images that you
> can create using the Docker files in the GitHub repository, or the
> images that are in DockerHub at
>
> https://hub.docker.com/u/sphericalcowgroup/dashboard/
>
> ?

The database image would be the app bootstrapped enough to reproduce an issue.

FWIW that link gives me a 404, maybe it's not public.

I do see :

 https://hub.docker.com/u/sphericalcowgroup/
 https://hub.docker.com/u/sphericalcow/

but without a public Dockerfile I can't say what the difference would
be (without downloading and running those containers).

[keep in mind I'm a docker-dork]

> Put another way, how will your "starting point" differ specifically from
> what you get if you spin up one of the containers now?

A CO with at least one user and two extended attributes. I think
that's what you are asking.

> You can use docker commit to essentially snapshot a running container
> into a distributable image.

Ah, nice.

> support auto-loading of SQL at first boot if it is put inside the image
> in a known place. That would probably lead to a more manageable process
> since you could put the SQL under version control.

I was thinking REST API, hadn't thought about SQL.

> bootstrap ... "script" a batch of actions when a new CO is created

I was going to ask if there was a non-REST API, not sure if that would
be up to the framework or app though.

But, yes, the setup script could call/execute a local PHP file, at the
simplest. Just not sure what code can be called.

Hope I'm making sense ...
Tom