![]() ![]() # Turn on WebDAV sharing and only allow user accounts in the posix group “staff” to access it. It should look like our example omnipresence share that we’ve configured below: # Map the URL /omnipresence to the filepath that we want to host a WebDAV share.Īlias /omnipresence "/Volumes/System/Users/Shared/OmniPresence/" Remove the example configuration’s Directory directive block and replace it with your own configuration. ![]() We will edit it to define a single share called “omnipresence” that uses OS X’s user and group accounts to control access. The example configuration file outlines how a WebDAV share is defined. If your configuration file has any errors in it the Apache service will not start. Note: any file that you put in /Library/Server/Web/Config/apache2/sites/ that ends in “.conf” will be included by OS X Server in the Apache configuration when the Websites service is started. cp /etc/Apache2/original/extra/nf /Library/Server/Web/Config/apache2/sites/nf In this case we chose nf but you can name it whatever makes the most sense to you. The example configuration file is located at: /etc/Apache2/original/extra/nfĬopy this file to the website configuration path with a new filename. Make a copy of the example WebDAV configuration file and move it to OS X Server’s website configuration directory. ![]() It goes into more operational details about what they’ve configured and what you may and may not touch.Īssuming that you have never used Apple’s built-in file sharing feature to host WebDAV configuring Apache is fairly straightforward. Take particular note of Apple’s ReadMe.txt file ( /Library/Server/web/config/Apache2/ReadMe.txt). While Apple’s documentation is sparse, they do outline what directories are used for configuration files, which is a great place to start poking around. However, all files and folders must be owned by the Apache web server (_There is an overview of Apple’s configuration of the Apache httpd server see their documentation website. You will also be able to use posix group permissions to control access to the shares. This configuration will emulate Apple’s configuration by allowing you to login to a WebDAV share using system account credentials. You should also be comfortable with the command line. This requires some knowledge of both the Apache web server and Apple’s implementation. Instead of using OS X Server’s built-in file sharing WebDAV configuration, we recommend manually configuring a WebDAV share by editing the appropriate Apache configuration file. We don’t recommend using it at this time. In our experience this configuration has had a number of hard-to-identify bugs that can corrupt your data. However, this WebDAV implementation is a fairly complex configuration that utilizes a proxy to create Apache processes that run as user accounts. OS X Server includes WebDAV as one of the options for file sharing. These instructions are offered as guidance for those interested in self-hosting, but should not be considered a comprehensive overview of the Apache implementation process. You should be comfortable with the responsibilities of maintaining a server, including keeping your Mac up to date with the latest security patches. These steps assume that you’re familiar with the Apache web server and understand this risk. IMPORTANT: When you expose files and folders on your computer to the internet (even with password protection), you assume some risk. Please note: due to the wide array of possible setup configurations and outside factors involved with custom hosting setups, troubleshooting, setting up, or administering WebDAV servers is beyond the scope of the tech support we are able to provide. Learn more about setting up iCloud Drive. For current versions of OmniOutliner, OmniGraffle and OmniPlan, Omni recommends syncing via iCloud Drive, because of its reliability, accessibility and direct system integration. ![]() OmniPresence is a legacy solution for syncing documents across iOS and macOS devices. ![]()
0 Comments
Leave a Reply. |