What's new in WebDAV in CF9?
We got some revision control in your WebDAV! But don't worry if you've got a RCS process you like already, dislike Subversion, or aren't ready for jumping in to RCS - it's almost entirely invisible, and if you don't want to use it, you needn't know that it's there. You can continue to use any DAV client that you like that works with kProxy 2 and DAVPortal. DAV paths are set up very similarly to how they have always been, with most of the adaptations made to handle the VM-model used in CF9.
Using a traditional DAV client
Using kProxy 2
- Enter https://hosting-webdav.kproxy.cornell.edu/cf9-YOUR-CUSTOMER-NAME (you should have received this url when your instance was created) into your favorite DAV client
- When prompted, enter your NetID and kerberos password
- Use DAV as normal
Using DAVPortal
- Enter https://hosting-webdav.kproxy.cornell.edu/cf9-YOUR-CUSTOMER-NAME into your favorite DAV client
- Visit http://hosting-webdav.cit.cornell.edu/davlogin to acquire your DAVLogin key
- When prompted by your client, enter your NetID and DAVLogin key
- Use DAV as normal
Integration into existing practices
If you have an existing practice with a revision control system of your choice that interacts with other CIT DAV services, your practice shouldn't need to change for use with CF9.
The only caveat is that you may want to ensure that any hidden files used by the source control system (e.g. .svn/ or .git/) are not pushed up to the DAV share, as our Subversion will then version them. In the case of .svn/, pushing it up may cause conflicts with the server-side Subversion.
Using a Subversion client with your DAV process
Using kProxy 2
- Your repository URL will be https://hosting-webdav.kproxy.cornell.edu/cf9-YOUR-CUSTOMER-NAME - standard Subversion clients (with HTTPS support) should work fine with this path
- Your username and password are your Kerberos credentials
Using DAVPortal
- Your repository URL will be https://hosting-webdav.kproxy.cornell.edu/cf9-YOUR-CUSTOMER-NAME
- Your username will be your NetID and your password will be your DAVLogin key, acquired from http://hosting-webdav.cit.cornell.edu/davlogin
Notes for both
- Interactions with the repository will be tagged with your NetID automatically
- Any Subversion client should work, including the command line utilities. It will need to have HTTPS support built in to work with kProxy 2.
- Further restriction of access to repositories is available using CUWA2
- There are otherwise no restrictions on the functionality provided - it's a standard repository export over
mod_dav_svn
git-svn or hg-svn
We have not yet had the chance to test git or hg's Subversion bridges with this system and welcome any testing or feedback from the user community.