On 3/17/15, Jan Nijtmans <jan.nijtm...@gmail.com> wrote: > 2015-03-17 22:18 GMT+01:00 Richard Hipp <d...@sqlite.org>: >> What is the proposed purpose of the --docker option to "fossil init"? >> Presumably it has something to do with the Docker container system. >> But I do not understand what that is, exactly? Why does Fossil need >> special options in order to work with Docker? > > The easiest way to try this, is to type the following on > any system which has Docker installed: > sudo docker run -d -p 8080:8080 nijtmans/fossil > See: > https://registry.hub.docker.com/u/nijtmans/fossil/ > > "fossil init --docker" produces a repository without > project-id and server-id. This repository is not usable > as-is. But as soon as "docker server" is started, > that's when the project-id and server-id is > generated. Without the --docker option all fossil > docker containers in the whole world would > have the same project-id and server-id. >
Trunk now supports the --create option to "fossil server" which creates the repository if it does not exist. This seems like a safer approach that trying to half-create a repository when the docker is instantiation and then finishing the creation process when the docker is first run. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev