![]() # seahub # SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 # seafile fileserver # ProxyPass /seafhttp # Use "DocumentRoot /var/www/html" for CentOS # Use "DocumentRoot /var/www" for Debian/Ubuntu DocumentRoot /var/www Alias /media /opt/seafile/seafile-server-latest/seahub/media AllowEncodedSlashes On RewriteEngine On Require all granted Second, a SSL certificate is integrated in the Apache configuration. The setup proceeds in two steps: First, Apache is installed. If your setup differs from thes requirements, adjust the following instructions accordingly. A host name points at the IP address of the server and the server is available on port 80 and 443.Seafile Server Community Edition/Professional Edition was set up according to the instructions in this manual.This manual assumes the following requirements: The setup of Seafile using Apache as a reverse proxy with HTTPS is demonstrated using the sample host name. You find instructions for enabling HTTPS with Nginx here. The full documentation of Apache is available at. Apache, a popular web server and reverse proxy, is a good option. If you have a SSL certificate from another CA, skip the section "Getting a Let's Encrypt certificate".Ī second requirement is a reverse proxy supporting SSL. Unless you already have a SSL certificate, we recommend that you get your SSL certificate from Let’s Encrypt using Certbot. HTTPS requires a SSL certificate from a Certificate Authority (CA). ![]() While HTTP is ok for testing purposes, switching to HTTPS is imperative for production use. Deploy Seahub at Non-root domain or on custom portĪfter completing the installation of Seafile Server Community Edition and Seafile Server Professional Edition, communication between the Seafile server and clients runs over (unencrypted) HTTP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |