Apache WebDAV

Apache WebDAV is a lightweight WebDAV (Web Distributed Authoring and Versioning) server for self-hosted file access.

  • Cloud
Apache WebDAV is a lightweight WebDAV (Web Distributed Authoring and Versioning) server for self-hosted file access. It exposes a directory over HTTP so compatible clients can browse, upload, download, and synchronize files. It is aimed at homelab users who want a simple, low-configuration file-sharing endpoint without a full cloud suite. Use it when a minimal Apache-based WebDAV server is sufficient and you already have a WebDAV client; it does not include a browser web interface.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

30/100 Low

Maintained
0last commit 1715 days ago
Popular
3133 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 55 days ago

GitHub stars
33
Open issues
3
Last commit
2022-03-12
License
MIT
Activity
stale

Checked yesterday - source: GitHub (mgutt/docker-apachewebdav)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Multi-user authentication Default authentication uses the USERNAME and PASSWORD environment variables for one user. For multiple users, bind-mount a user.passwd file to /user.passwd and populate it with htpasswd in the container console, for example: htpasswd -B /user.passwd username. source

Fetched 51 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I put the WebDAV container behind a reverse proxy for HTTPS?

Use a reverse proxy to handle SSL certificates, or set SSL_CERT=selfsigned to generate a self-signed certificate. You can also bind-mount a certificate chain to /cert.pem and a private key to /privkey.pem.

How do I support multiple usernames and passwords?

USERNAME and PASSWORD support only a single user. Bind-mount your own file to /user.passwd and populate it with htpasswd for Basic authentication or htdigest for Digest authentication.

Which directories should I volume-mount for files and container state?

Mount the exposed files to /var/lib/dav/data and the container's app data to /var/lib/dav.

What port does the basic container expose?

The basic example runs the WebDAV server on port 80.

What does the 'Could not open the lock database' error mean?

It means the Apache user and group do not have write access to the lock database file and its directory.

Answers sourced from github.com, serverfault.com

Community

Collected 54 days ago - public community threads