Relitive paths with ssh
Martin Pool
mbp at sourcefrog.net
Wed Jul 8 02:09:59 BST 2009
2009/7/8 <hessiess at hessiess.com>:
> Yep, I worked that out after the last post. It also makes it virtually
> imposable to checkout the latest revision into the web root. Uploading the
> entire file simply isn't an option for me as I end up spending more time
> waiting for stuff to upload than actually coding. Im probably going to end
> up using SVN unless someone has any other suggestions, at least it has
> decent support for webdav, removing the need for proxy tunnelling and such
> like.
Hang on a bit, this seems very unrelated to supporting
homedir-relative paths and I don't understand precisely what you're
trying to do, or what you mean by 'uploading the entire file'.
You want the contents of the branch visible on the web server.
It's not clear to me whether you want the branch history stored there
too, or whether you want to pull it onto the web server from some
other machine. If it's the second, you just need to create the right
checkouts on the server then periodically run 'bzr update' in them to
update the tree.
The limitation with ssh urls (pending
https://bugs.edge.launchpad.net/bzr/+bug/109143 being finished and
merged) is just that you can't directly refer to the home directory.
You can certainly do bzr+ssh://user@host/home/user/thing
--
Martin <http://launchpad.net/~mbp/>
More information about the bazaar
mailing list