About This Service provides project hosting based on a simple threefold principle:

  • Provide storage to users as a centralized “commodity utility” (like electricity).

  • Export that storage over a variety of protocols (SMTP, AFS, HTTP, NNTP, etc).

  • Let users specify access controls on an inter-organization, fine-grained basis.

What Does It Support?

Currently, this server lets you access your files one of four ways:

  • AFS, the Andrew FileSystem protocol (using OpenAFS).
    This is by far the preferred way to access your files; it is the fastest, you can use it to change permissions, and it works through firewalls.
    AFS instructions are here

  • HTTP (using UMich's filedrawers)
    This will work from any web browser. It is slower, but still allows you to change permissions, and works through both firewalls and proxies.
    HTTP instructions are here

  • WebDAV (using mod_dav)
    This will let you browse your folders using the Mac OS X Finder or Windows Explorer. It pretty slow, and won't even let you change permissions, but at least it works through both firewalls and proxies.
    WebDAV instructions are here

  • SVN (using mod_svn)
    You can place subversion repositories in AFS space and check changes in via Apache without having to install the AFS client. Access control is done via AFS acls, so you no longer need to have a special “subversion accounts” for each project.
    Subversion instructions are here

Do I need an account?

If you have a UC Berkeley EECS Account or a UC Berkeley CalNet account, you already have an account on this service – we have arranged cross-realm authentication with these departments. When logging on, always use your username/studentid plus “@” and the appropriate domain. The domain must be capitalized.

At the request of the CalNet administrators, support for CalNet authentication via HTTP has been temporarily disabled.

gradstudent@EECS.BERKELEY.EDU (EECS account)
12345678@BERKELEY.EDU (student CalNet)
drfamous@BERKELEY.EDU (faculty CalNet)

We can set up additional cross-realm authentication with any other organization that uses Kerberos (nearly every university already does). We can also create “local-only” accounts for individuals who are not affiliated with an organization that uses Kerberos.