WebDAV with a Quota? 44
gik asks: "I'm in the need for a quota-managing, multi-account capable, class-1 WebDAV server (for remote file storage for clients). I've been researching WebDAV for a long long time now, and have only found one all-in-one implementation: Xythos webfile server, which is a very costly (but a very good) solution. I know that some online storage companies use a hacked Apache, but as anyone who's worked with WebDAV knows, doing this with Apache can be hard. So I'm asking: Does anyone out there know of a good WebDAV server with (hopefully) quota management that is as reliable and free as Apache? Oracle's IFS, Novell Netware, and the like are acceptable as possible candidates."
IIS (Score:4, Funny)
Re:IIS (Score:2)
(IIS being designed for "intranets" while Apache is designed for internet sites.)
Re:IIS (Score:2)
They are handled just like they are with a local user or with CIFS. Sharing a folder with WebDAV/IIS is functionally equivilent to sharing it with CIFS.
Enabling WebDAV on Apache (Score:3, Informative)
Re:Enabling WebDAV on Apache (Score:1)
Reading the link, sounds a lot like (groan) FrontPage... Since I know this can not be the case, could one of the learned Slashdotters explain to me what WebDAV means?
Re:Enabling WebDAV on Apache (Score:3, Informative)
Reading the link provides the following explaination:
Re:Enabling WebDAV on Apache (Score:2)
Wow, FTP.. Again.
Re:Enabling WebDAV on Apache (Score:2)
Re:Enabling WebDAV on Apache (Score:2)
First off, who cares? The topic of this story has nothing to do with FTP. It has to do with finding a webserver which allows an easy setup of WebDAV.
That said, this is different from FTP as it uses HTTP extensions to operate. Let's remind ourselves what FTP does -- tranfers files. That's it. In order to edit remote files, you would have to download the file locally, make your changes, and upload it again. The FTP protocol does not allow the same functionality as WebD
Re:Enabling WebDAV on Apache (Score:2)
Actually, it has the benefit of allowing more access controls than traditional FTP - hence the name, "authoring and versioning".
Frontpage extensions vs. WebDAV (Score:5, Informative)
WebDAV attempts to standardize this kind of functionality and make it available to many more programs and across platforms. WebDAV is sufficiently functional, complete, and efficient to serve both as a network file system protocol and as a network-based version control system.
Re:Enabling WebDAV on Apache (Score:2)
However, given the importance of WebDAV, I think mod_dav should become a standard, default part of every Apache install; the only thing users should have to do to enable access is set up passwords for their users.
Re:Enabling WebDAV on Apache (Score:1)
Patch for quotas (Score:3, Informative)
Quota (Score:4, Interesting)
Re:Quota (Score:3, Informative)
Re:Quota (Score:2)
Re:Quota (Score:1)
Re:Random Thought (Score:1)
Re:Quota (Score:2)
Otherwise a nice perl script in my homedir could wipe out everything owned as "www" (like the main webpage).
Yep, welcome to the world of shared web hosting.
Re:Quota (Score:4, Informative)
I get the feeling that Apache was designed for providing uploads to clients only, not full scale IO, and that mod_dav is a bit of an afterthought for trusted users.
BTW: This mod (and Apache) specifically provide no support for quotas:
Re:Quota (Score:2, Interesting)
Just thought I'd note if you use a dav cgi script you can potentially utilize that to achieve quotas, depending on how much you trust your script you could make the cgi script setuid root and then authenticate against /etc/shadow (bad idea on non ssl connection btw) and from there immediately setuid to the user you authenticate as. From here standard OS quotas will indeed take effect.
The problem is if someone finds a flaw in your script then they can r
Re:Quota (Score:2)
If someone finds a flaw in your script, they can ownz0r all your users, but not have root
Zope, perhaps (Score:4, Informative)
You would use Zope as a dumb, albeit journaled and transactional, file storage, though the files themselves will be stored in an opaque (object database) format; in other words, the only way to access the files will be through WebDAV (or FTP, which Zope also supports).
Re:Zope, perhaps (Score:1)
ezPublish CMS has WebDAV capabilities (Score:3, Informative)
Since it's based on PHP and pretty extensible, I would think getting a quota function established (if eZ publish doesn't already have one) would be easy enough.
Now, can someone help me get the damned 3.4.4 version to run on FreeBSD? ;)
Obligatory 10-second Google search (Score:3, Informative)
iDisk (Score:3, Interesting)
Apple's iDisk [mac.com] offering is, or at least once was, WebDAV. Also incorporates quotas and is multi-user capable. Allows them to give nice hooks to publishing directly from iMovie and iPhoto, for example.
Sorry, I don't know exactly how they do it; but I do know that when it was announced (in '99?) there was some discussion about how Apple was accomplishing it. And you could probably reverse-implement their implementation in a few hours of poking.
For that matter, I think SpyMac [spymac.com] uses the same thing.
WebDAV without Apache? (Score:3, Informative)
My main server is a low-end notebook. It passes packets, does SMTP, file serving etc quite nicely. Unfortunately apache is just way too heavyweight for it; I use thttpd [acme.com] instead, which is smaller and faster.
I'd like to set up a WebDAV server. But I don't want to have to replace thttpd. Are there any small, light tools that will just do WebDAV and nothing else, that I can add to my setup?
Re:WebDAV without Apache? (Score:2)
Try loading Apache with just the barest essentials of modules (core functionality in Apache 2). The resource footprint ain't very big. Also, in terms of speed, Apache 2 can use the sendfile(...) API [apache.org], memory map resources [apache.org], and mod_cache [apache.org] if you load in support for it. In this configuration, you can easily saturate a gigabit ethernet connection. So unless you've got
Re:WebDAV without Apache? (Score:2)
Stock Apache on my server came in at about 5-10MB RSS. thttpd is currently ticking away at 976kB. Apache takes >15s to start, thttpd starts instantly. Apache is too heavyweight for me. (My server is grossly underpowered, yes, but size and budget constraints mean I can't upgrade it.) Now then, on to WebDAV. Your comment, "Are there any small, light tools that will
Re:WebDAV without Apache? (Score:2)
Another note, are you running out of memory on the box? Unless you're using up >95% of available memory (and thus beginning to swap heavil
Re:WebDAV without Apache? (Score:2)
A P133 notebook with 48MB of RAM.
So you can probably understand why I'm anxious to keep memory usage down! And yes, I know I should upgrade it, but it's harder than you might think. While I do have 128MB of laptop memory in hand, the blasted notebook can't handle DIMMs larger than 16MB. (It's got two 16MB DIMMs, plus another 16MB internally.)
There are two main reasons for using such an underpowered machine: firstly, cost, and secon
public_html+webdav (Score:1)
Turn the gid bit on for the public_html directories.
Turn on group quotas for the partition.
Add www-data to each of the user's unique groups.
Careful though. This server will only be suitable for webdaving as adding www-data to many groups may make things very insecure if youre allowing your users to do scripting, ssh in or things like that.
Funny. (Score:2)
With this in mind, it is probably less surprising that Novell also offers this functionality on the Linux platform using SuSE Linux Enterprise Server 8/9 [novell.com] and Novell Nterprise [novell.com] services for Linux.
Great. Now I sound like a shill.
Re:Funny. (Score:1)
Not webDAV, but why not: (Score:1)