Simple LAN filesharing with WebDAV - Revision history

320x200: /* Linux filesystem */

2024-12-30T12:33:59Z

Linux filesystem

← Older revision		Revision as of 12:33, 30 December 2024
Line 80:		Line 80:
	sudo apt install davfs2		sudo apt install davfs2
	sudo mount -t davfs http://192.168.100.100/readonly /mnt/readonly		sudo mount -t davfs http://192.168.100.100/readonly /mnt/readonly
	* To remember username passwords you can create a personal <code>~/davfs2/secrets</code> file with:		* To remember username passwords you can create a personal <code>~/.davfs2/secrets</code> file with:
	http://192.168.100.100/readwrite1 turtleprincess heygirl		http://192.168.100.100/readwrite1 turtleprincess heygirl
	http://192.168.100.100/readwrite2 turtleprincess heygirl		http://192.168.100.100/readwrite2 turtleprincess heygirl
	etc		etc
			* permissions matters
			chmod 600 ~/.davfs2/secrets
	* You can also have everything configured in your <code>/etc/fstab</code> and then mount everything as a regular user:		* You can also have everything configured in your <code>/etc/fstab</code> and then mount everything as a regular user:
	<pre>		<pre>

320x200: /* Pro Tips */

2024-03-18T23:16:18Z

Pro Tips

← Older revision		Revision as of 23:16, 18 March 2024
Line 154:		Line 154:
	systemctl restart lighttpd		systemctl restart lighttpd

	[[Category: ~~Backup]]~~		[[Category: WebDAV]]
	~~[[Category: LAN]]~~
	~~[[Category: File Sharing~~]]

320x200: /* Pro Tips */

2024-03-10T19:38:18Z

Pro Tips

← Older revision		Revision as of 19:38, 10 March 2024
Line 145:		Line 145:
	== Pro Tips ==		== Pro Tips ==
	* IPs are used above but you can use a local DNS or make use of your local <code>/etc/hosts</code> files to give a nice name to your WedDAV server, look into RFC 8375 for pointers.		* IPs are used above but you can use a local DNS or make use of your local <code>/etc/hosts</code> files to give a nice name to your WedDAV server, look into RFC 8375 for pointers.
			* To debug things if things are not behaving as nice things:
			lighttpd-enable-mod accesslog
			systemctl restart lighttpd
			tail -f /var/log/lighttpd/access.log
			# 17.4 hours later
			# Problem solved at last
			lighttpd-disable-mod accesslog
			systemctl restart lighttpd

	[[Category: Backup]]		[[Category: Backup]]
	[[Category: LAN]]		[[Category: LAN]]
	[[Category: File Sharing]]		[[Category: File Sharing]]

320x200: /* FreeBSD filesystem */

2024-03-02T23:47:00Z

FreeBSD filesystem

← Older revision		Revision as of 23:47, 2 March 2024
Line 123:		Line 123:
	* in <code>/etc/fstab</code>		* in <code>/etc/fstab</code>
	<pre>		<pre>
	# ~~WedDAV stuff~~		# My cool LAN WebDAV thing
	192.168.100.100:readonly /mnt/readonly fuse noauto,ro,mountprog=/usr/local/bin/mount.rclone		192.168.100.100:readonly /mnt/readonly fuse noauto,ro,mountprog=/usr/local/bin/mount.rclone
	192.168.100.100:readwrite1 /mnt/readwrite1 fuse noauto,rw,mountprog=/usr/local/bin/mount.rclone		192.168.100.100:readwrite1 /mnt/readwrite1 fuse noauto,rw,mountprog=/usr/local/bin/mount.rclone

320x200 at 23:40, 2 March 2024

2024-03-02T23:40:00Z

← Older revision		Revision as of 23:40, 2 March 2024
Line 145:		Line 145:
	== Pro Tips ==		== Pro Tips ==
	* IPs are used above but you can use a local DNS or make use of your local <code>/etc/hosts</code> files to give a nice name to your WedDAV server, look into RFC 8375 for pointers.		* IPs are used above but you can use a local DNS or make use of your local <code>/etc/hosts</code> files to give a nice name to your WedDAV server, look into RFC 8375 for pointers.

			[[Category: Backup]]
			[[Category: LAN]]
			[[Category: File Sharing]]

320x200: /* Android */

2024-03-02T23:39:06Z

Android

← Older revision		Revision as of 23:39, 2 March 2024
Line 133:		Line 133:

	=== Android ===		=== Android ===
	Several commercial, closed source options. ~~Three~~ interesting FLOSS options:		Several commercial, closed source options. We don't talk to these people. There are however three interesting FLOSS options:
	* https://github.com/newhinton/Round-Sync - super complete, multiple network file storage supported (based on rclone)		* https://github.com/newhinton/Round-Sync - super complete, multiple network file storage supported (based on rclone)
	* https://github.com/phpbg/easysync - minimal automated WebDAV sync for the usual Android user data folders		* https://github.com/phpbg/easysync - minimal automated WebDAV sync for the usual Android user data folders

320x200: /* Nautilus */

2024-03-02T23:38:21Z

Nautilus

← Older revision		Revision as of 23:38, 2 March 2024
Line 130:		Line 130:

	=== Nautilus ===		=== Nautilus ===
	For those into GUI, WebDAV is really to access thanks to the ~~gvfs~~ daemon. It's also a solid option in terms of recovery and making sure little to no fuckery is possible when writing on an unstable network. In practice, click on the "other" location button on the left pane, choose WedDAV and enter the URL in the form of <code>dav://192.168.100.100/readwrite1</code> and give your credentials. The only caveat is that the mounted folder name will be the server name, only the server name (IP in this case), so you may want to add your share to the bookmarks, and rename the bookmark to something more meaningful.		For those into GUI (not judging, it's a free country) WebDAV is really easy to access thanks to the GVfs daemon. It's also a solid option in terms of recovery and making sure little to no fuckery is possible when writing on an unstable network. In practice, click on the "other" location button on the left pane, choose WedDAV and enter the URL in the form of <code>dav://192.168.100.100/readwrite1</code> and give your credentials. The only caveat is that the mounted folder name will be the server name, only the server name (IP in this case), so you may want to add your share to the bookmarks, and rename the bookmark to something more meaningful.

	=== Android ===		=== Android ===

320x200: /* FreeBSD filesystem */

2024-03-02T23:36:21Z

FreeBSD filesystem

← Older revision		Revision as of 23:36, 2 March 2024
Line 93:		Line 93:

	=== FreeBSD filesystem ===		=== FreeBSD filesystem ===
	At time of writing, davfs2 is being ported to FreeBSD by its author. Don't hold your breath, but hopefully this will ~~be finalized~~ because FreeBSD usual way to mount WebDAV stuff with just sucks (~~problems when~~ reading ~~data directly~~, ~~problems~~ when the server disconnects). As a workaround, the ~~project~~ rclone is the only ~~decent~~ way to have WebDAV mounted in a FreeBSD filesystem.		On FreeBSD it's basically the same as on Linux. lol. Of course not! What did you think? That would be too easy. You need to work hard to earn your condescending smug BSD coolness. At time of writing, <code>davfs2</code> is being [https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267518 ported to FreeBSD by its author]. Don't hold your breath, but hopefully this will happen because the FreeBSD usual way to mount WebDAV stuff with <code>mount.webdavfs</code> just sucks ("Device not configured" on certain reading operations, not able to recover when the server disconnects). As a workaround, the all-you-can-eat-software-buffet <code>rclone</code> is the only reliable way to have WebDAV mounted in a FreeBSD filesystem.

			* installation
			pkg install rclone # yeah yeah you can use portmaster and disable stuff you will regret later
	* load fuse		* load fuse
	sudo kldload fusefs		sudo kldload fusefs

320x200: /* Linux filesystem */

2024-03-02T23:20:46Z

Linux filesystem

← Older revision		Revision as of 23:20, 2 March 2024
Line 76:		Line 76:

	=== Linux filesystem ===		=== Linux filesystem ===
	Mounting a WebDAV on Linux is straightforward with <code>davfs2</code> and requires minimal configuration. <code>davfs2</code> is also able to recover quite well from disconnections and potential read/write fuckery (there is a daemon and a local cache, but you don't need to worry about this). If the server is dead, that you need to poweroff your machine, and you still have something mounted, it's a good idea to unmount things first to speed up shutdown. No it won't lock like a shit ~~like NFS does~~ but there is a timeout ~~trigger~~.		Mounting a WebDAV on Linux is straightforward with <code>davfs2</code> and requires minimal configuration. <code>davfs2</code> is also able to recover quite well from disconnections and potential read/write fuckery (there is a daemon and a local cache, but you don't need to worry about this). If the server is dead, that you need to poweroff your machine, and you still have something mounted, it's a good idea to unmount things first to speed up shutdown. No it won't lock like a little NFS shit but there is a timeout and you're a busy person.
	* To mount manually the read-only folder from above:		* To mount manually the read-only folder from above:
	sudo apt install davfs2		sudo apt install davfs2

320x200: /* Example Configuration */

2024-03-02T23:17:17Z

Example Configuration

← Older revision		Revision as of 23:17, 2 March 2024
Line 61:		Line 61:
	</pre>		</pre>

	Now if you wonder what kind of magic will happen so that the lighttpd process, local and remote users can happily edit the same files, well, none. It won't work and you will be sad. Then you will start binge drinking to forget about server administration, go in the streets pick up fights with strangers who are in a much better physical condition because they don't spend hours configuring neovim plugins that you ~~don~~'t even ~~use~~. It will be painful. To avoid this unfortunate situation you need to do two things:		Now if you wonder what kind of magic will happen so that the lighttpd process, local and remote users can happily live together ever after, and edit the same files, well, none. It won't happen just like this, it does not work and you will be sad. Then you will start binge drinking to forget about server administration. You will go in the streets, pick up fights with strangers who are in a much better physical condition because they don't spend hours configuring neovim plugins that ''you haven't even used once''. It will be painful. So to avoid this unfortunate situation you need to do two things:
	* First, the folder needs to be group-owned by the lighttpd process owner, in ~~this~~ <code>www-data</code> ~~and you~~ also need to set the group ID bit on the folder, so that all newly created files will inherit the group ownership.
			* First, the folder needs to be group-owned by the lighttpd process owner, in our case, on Debian, it's <code>www-data</code>. You also need to set the group ID bit on the folder you intend to use as WedDAV share, so that all newly created files will inherit the group ownership of this folder.
	sudo chown regular_user:www-data /local/path/to/readwrite1		sudo chown regular_user:www-data /local/path/to/readwrite1
	sudo chmod g+ws /local/path/to/readwrite1		sudo chmod g+ws /local/path/to/readwrite1
	* Second, you need to change the way lighttpd is started so that its umask is set in a way that any permission may be set for user and group (default is just user). On a systemd based system you need to edit <code>/etc/systemd/system/lighttpd.service</code> ~~so that~~:		* Second, you need to change the way lighttpd is started so that its umask is set in a way that any permission may be set for user and group (default is just user). On a systemd based system (haters gonna hate) you need to edit <code>/etc/systemd/system/lighttpd.service</code> like this:
	ExecStart=/bin/sh -c 'umask 002;/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf'		ExecStart=/bin/sh -c 'umask 002;/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf'

	That's it, you have a working simple LAN filesharing with WebDAV check the documentation for more options, and more fun config time.		That's it, you have a working simple LAN filesharing with WebDAV check the documentation for more options, and more fun config time, at home, where it's much safer for you.

	== Client side ==		== Client side ==