# Self-host WebDAV Server

> Small standalone WebDAV server with per user permissions. The install form carries config.yml as an editable file and a generated admin password.

- Page: https://levelrail.com/templates/webdav/
- JSON: https://levelrail.com/templates/webdav.json
- Category: Storage
- Licence: MIT (Permissive license)
- Source: https://github.com/hacdias/webdav
- Upstream docs: https://github.com/hacdias/webdav#readme

## Requirements
- Memory: about 32 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: v5.17.3

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| webdav | hacdias/webdav | v5.17.3 | 6060 | data -> /data |

## Deploy

### CLI

```bash
levelrail-cli templates install webdav --name my-webdav
```

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain webdav=app.example.com.

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/webdav/install \
  -d '{
    "name": "my-webdav"
  }'
```

Create a token in the dashboard first. Name, env and domains are the request fields.

## First run
1. Connect a WebDAV client to the address with the user admin and the generated password shown in the deployment variables.

## Questions

### Can I deploy WebDAV Server on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for WebDAV Server, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image hacdias/webdav:v5.17.3 is what you deploy there.

Self-host WebDAV Server, WebDAV Server docker compose file, deploy WebDAV Server on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
