![]() ![]() Public IP: 120.118.8.10 ( Please note this is a FAKE IP)įor the scenario presented, any entry-level cloud server will suffice, as long as it has a public IPv4 address.Operating System: Ubuntu Server 22.04 AMD64.Suppose we have a cloud service with the following specifications: Object Storage + Network Database: When you need both more storage space, and expose JuiceFS as a distributed file system.Object Storage + Standalone Database: When you need more storage capacity.Local disk + Standalone Database: When there is enough space available on the local disk of the cloud server.Therefore, the JuiceFS data storage and metadata engine can be built with more flexibility, for example: To make our WebDAV accessible over the Internet, we will then create it on a cloud server with a fixed public IPv4 address, then it can be accessed everywhere via IP address or domain name. Metadata engine is used to store the metadata of the files, which can use network-based databases such as Redis, MySQL, PostgreSQL, or standalone databases such as SQLite or BadgerDB. JuiceFS file system consists of two parts: data storage and metadata engine, data storage can be object storage services provided by various public cloud services, or self-hosted MinIO or local disk. Therefore, you need to create a JuiceFS file system in advance. The WebDAV share presented in this article is an access interface provided by JuiceFS and is built on top of the JuiceFS file system. The following content demonstrate how to configure a WebDAV service on top of JuiceFS. JuiceFS provides POSIX, S3 API, HDFS API, Kubernetes CSI driver, Docker Volume Plugin, WebDAV access, making it easy to work with various applications. JuiceFS is a open source distributed file system designed for the cloud, relying on object storage and database, and can quickly build a high-performance storage system with elastic capacity. If you are looking for a more general, efficient, and simple solution for configuring WebDAV, JuiceFS may be an ideal option. While some NAS operating systems will also provide WebDAV shared configuration capabilities, they are limited by the intranet environment, making it difficult to share across the internet. In the past, configuring WebDAV shares usually involves using web server software such as Apache HTTP service or Nginx, which adds complexity since since these modules were not available out of the box. WebDAV sharing), which corresponds to the “blue cloud” part of the architecture diagram. With a basic understanding of the WebDAV architecture, let's configure our own WebDAV server (i.e. WebDAV Client: A variety of programs with built-in WebDAV clients that run on your phone, tablet, or computer.WebDAV Server: The blue cloud represents the WebDAV server, which stores data in response to client read/write requests.In order to avoid confusion, it is necessary to clarify the concepts related to WebDAV, which consists of two parts: the server and the client, as shown in the following figure. This means that with your own WebDAV storage, you can use WebDAV to save data from these software anytime and anywhere. There are a large number of mobile and PC applications with built-in support for WebDAV, such as the well-known document management tool Zotero, the popular note-taking tool Notability on iPad, the cross-platform Markdown note-taking tool Joplin, ES file manager, etc. WebDAV is an HTTP-based file sharing protocol originally designed for multi-user document collaboration, and is also widely used in Internet-based file storage, data synchronization, and other scenarios.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |