2015-03-18 15:20 GMT+01:00 Richard Hipp <d...@sqlite.org>: > 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.
Yes, I can see the advantage of that, but it's not a complete solution yet. When running fossil within Docker, there are two ways to fill the repository with artifacts: 1) If the container is intended to server a new repository, a client will simply clone the repository and start committing. All is well in this case. 2) If the container is intended to host an already existing repository, the project-id needs to be modified (using sql) and an external fossil somewhere will do a sync. This approach will result in the Chiselapp "I have two trunks" problem. Indeed, the --create option can be used as alternative to --docker, solving case 1). For 2) this is not a solution yet. Thanks! I will try this approach when fossil 1.33 is out, for now at least there is a working 1.32 fossil image with a solution for both 1) and 2). Jan Nijtmans _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
