On Fri, Nov 22, 2019 at 5:47 AM sebb <seb...@gmail.com> wrote: > > On Thu, 21 Nov 2019 at 17:00, Sam Ruby <ru...@intertwingly.net> wrote: > > > On Thu, Nov 21, 2019 at 10:11 AM sebb <seb...@gmail.com> wrote: > > > > > > That still causes issues for bundler. > > > Turns out this is caused by the line > > > - $HOME:/root > > > which causes bundler to use the wrong path. > > > I think it's unnecessary now anyway. > > > > That was an oversight, I meant to delete it. But if we were to > > symlink the home directory, I suspect that would have been useful to > > you as I gather you had symlinks in your /srv directory (presumably to > > locations within your home directory)? > > > > > Yes, my /srv/svn directory has links to some existing checkouts under my > home directory. > [That would require mounting $HOME:$HOME to preserve links, not $HOME:/root] > > But I was actually testing a separate docker workspace with its own SVN > checkout, as suggested in DOCKER.md > > > If I remove the line, SVN does now find the CA > > > I can interactively update SVN, however I am prompted for the password. > > > This means that 'rake svn:update' fails when logged in to the container > > > interactively. > > > And of course it does not work from the host as part of 'rake > > docker:update' > > > > Presuming that the subversion file system versions are compatible, you > > can do the svn:update and git:pull steps from the host. > > > > > Not really. > > If you are using a separate workspace for the container, the easiest way to > set it up is to run rake svn:update in the container > Running the command on the host will default to updating the host version. > > Once the checkouts have been set up, it would of course be possible to run > "svn up" separately on each of them on the host. > > > > > Somehow we need to get the password across to the container. > > > > Maybe not. Except for the few places where the whimsysvn user is used > > to enable access from non ASF-members, the password provided in the > > HTTP authentication is used. > > > > > > > Note: it's probably not necessary to mount the whole of HOME > > > One could mount just .subversion,.git and .ssh: > > > - $HOME/.subversion:$HOME/.subversion > > > - $HOME/.gitconfig:$HOME/.gitconfig > > > - $HOME/.ssh:$HOME/.ssh > > > > > > Maybe then replace the corresponding /root mounts with links. > > > > Done. > > > > Thanks! > That works for SVN and git when logged into the container. > > However there is now no rake command to populate the container /srv/svn. > Was that intentional?
I'm not fully understanding the behavior you are seeing. I gathered from your previous email that svn checkout would require some sort of prompting to you, and the container was not set up to prompt you. Specifically, you said "Somehow we need to get the password across to the container." Is that problem solved? So I intended to go the other way - have you do your svn up on on the host. My oversight was that I did not add a step (presumably to update ~/.whimsy) to configure where svn and git directories should be placed. I can rectify that, but first I want confirmation that I understand what you are seeing. Does svn checkout and svn up work as you would expect in the container? If so, we can go that way. Otherwise I can update the code and instructions to have you configure the location of the host directory. - Sam Ruby > > - Sam Ruby > > > > > On Thu, 21 Nov 2019 at 13:49, Sam Ruby <ru...@intertwingly.net> wrote: > > > > > > > On Thu, Nov 21, 2019 at 8:01 AM sebb <seb...@gmail.com> wrote: > > > > > > > > > > Might work better if the home directory was mounted directly as well? > > > > > > > > Give it a try > > > > > > https://github.com/apache/whimsy/commit/b4c7bc2f10a21078e44d0c8e528eab00da296ab2 > > > > > > > > - Sam Ruby > > > > > >
