Skip to content

README.md

Latest commit

 

History

History
62 lines (43 loc) · 2.22 KB

README.md

File metadata and controls

62 lines (43 loc) · 2.22 KB

Apache Webdav

The following tutorial uses Apache with Docker in Linux, using the image bytemark/webdav.

You can also checkout the official doc from Bytemark here. The tutorial you are reading here is a little different from Bytemark's article.

Assuming you want a webdav server on Linux satisfying that:

  1. Data is saved in your host machine's ./dav1 folder,
  2. WebDAV is accessed by a user user1 with password password1,
  3. WebDAV is accessed on the host machine and port 8080: 127.0.0.1:8080.
  4. Use Basic auth type.

Install docker nd set its permission properly. Then run this in terminal:

mkdir ./dav1 # create the local folder

docker container run --rm \
  -p 127.0.0.1:8080:80 \
  -v ./dav1:/var/lib/dav \
  -e USERNAME=user1 \
  -e PASSWORD=password1 \
  -e AUTH_TYPE=Basic \
  bytemark/webdav

We do not have --detach prameter here, so the server will be closed as soon as you terminate the program or close terminal. You might want to adjust the settings further by yourself.

Then, in Remotely Save's setting, set these (auth type should always be Basic):

Server: http://127.0.0.1:8080
User: user1
Password: password1
Auth Type: Basic
Depth Header Sent To Servers: only supports depth='1'

Apache RS Setting

Then the server should be connected! You can sync now!

In you host machine's file system, you should find some files and folders were added into the folder ./dav1.

ls ./dav1/
## data  DavLock  DavLock.dir  DavLock.pag

ls ./dav1/data/
## <your vault name or your base dir>

Auth type

You can change the auth type while calling Docker, between Basic and Digest. And please rememberto adjust the Remotely Save's settings. Both works.

Notice

  1. Never expose your webdav server to public networks without protections or without strong passwords!
  2. I personally recommend using tailscale to build a LAN instead of expoing the service to public.
  3. If you want to connect to the server from iOS (iPhone / iPad), the https is required. I personally recommend using caddy as the reverse proxy. Caddy can also be combined with tailscale.