Benutzer-Werkzeuge

Webseiten-Werkzeuge


wiki:seafile

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
wiki:seafile [2022/08/21 16:29] mhowiki:seafile [2022/08/22 18:10] (aktuell) mho
Zeile 1: Zeile 1:
 +<code>
 apt update && apt install mariadb-server mariadb-client apt update && apt install mariadb-server mariadb-client
 +</code>
  
 mysql_secure_installation mysql_secure_installation
Zeile 9: Zeile 11:
 Reload privilege tables now? [Y/n] y Reload privilege tables now? [Y/n] y
  
 +<code>
 mysql -u root -p mysql -u root -p
  
Zeile 40: Zeile 42:
  
 bash setup-seafile-mysql.sh bash setup-seafile-mysql.sh
 +</code>
 [ server name ] Seafile [ server name ] Seafile
 [ This server's ip or domain ] your_domain oder 192.168.178.x [ This server's ip or domain ] your_domain oder 192.168.178.x
Zeile 55: Zeile 57:
 [ seahub database ] seahub_server [ seahub database ] seahub_server
  
 +<code>
 echo "export LC_ALL=de_DE.UTF-8" >>~/.bashrc echo "export LC_ALL=de_DE.UTF-8" >>~/.bashrc
 echo "export LANG=de_DE.UTF-8" >>~/.bashrc echo "export LANG=de_DE.UTF-8" >>~/.bashrc
 echo "export LANGUAGE=de_DE.UTF-8" >>~/.bashrc echo "export LANGUAGE=de_DE.UTF-8" >>~/.bashrc
 source ~/.bashrc source ~/.bashrc
 +</code>
 Configuring the Apache Web Server Configuring the Apache Web Server
  
Zeile 66: Zeile 68:
  
 To begin forwarding requests, you will need to enable the proxy_http module in the Apache configuration. This module provides features for proxying HTTP and HTTPS requests. The following command will enable the module: To begin forwarding requests, you will need to enable the proxy_http module in the Apache configuration. This module provides features for proxying HTTP and HTTPS requests. The following command will enable the module:
 +<code>
     sudo a2enmod proxy_http     sudo a2enmod proxy_http
 +</code>
 Note: The Apache rewrite and ssl modules are also required for this setup. You have already enabled these modules as part of configuring Let’s Encrypt in the second Apache tutorial listed in the prerequisites section. Note: The Apache rewrite and ssl modules are also required for this setup. You have already enabled these modules as part of configuring Let’s Encrypt in the second Apache tutorial listed in the prerequisites section.
  
Zeile 74: Zeile 76:
  
 Open the configuration file in a text editor: Open the configuration file in a text editor:
 +<code>
     sudo nano /etc/apache2/sites-enabled/your_domain-le-ssl.conf     sudo nano /etc/apache2/sites-enabled/your_domain-le-ssl.conf
 +</code>
 The lines from ServerAdmin to SSLCertificateKeyFile are part of the initial Apache and Let’s Encrypt configuration that you set up in the prerequisite tutorials. Add the highlighted content, beginning at Alias and ending with the ProxyPassReverse directive: The lines from ServerAdmin to SSLCertificateKeyFile are part of the initial Apache and Let’s Encrypt configuration that you set up in the prerequisite tutorials. Add the highlighted content, beginning at Alias and ending with the ProxyPassReverse directive:
 /etc/apache2/sites-enabled/your_domain-le-ssl.conf /etc/apache2/sites-enabled/your_domain-le-ssl.conf
Zeile 226: Zeile 228:
  
 Create a systemd service file for the Seahub web interface: Create a systemd service file for the Seahub web interface:
 +<code>
     sudo nano /etc/systemd/system/seahub.service     sudo nano /etc/systemd/system/seahub.service
 +</code>
 This is similar to the Seafile service. The only difference is that the web interface is started after the Seafile service. Add the following content to this file: This is similar to the Seafile service. The only difference is that the web interface is started after the Seafile service. Add the following content to this file:
 +<code>
 Create /etc/systemd/system/seahub.service Create /etc/systemd/system/seahub.service
  
-<code> 
 [Unit] [Unit]
 Description=Seafile hub Description=Seafile hub
Zeile 252: Zeile 254:
  
 Finally, to enable both the Seafile and Seahub services to start automatically at boot, run the following commands: Finally, to enable both the Seafile and Seahub services to start automatically at boot, run the following commands:
 +<code>
     sudo systemctl enable seafile.service     sudo systemctl enable seafile.service
     sudo systemctl enable seahub.service     sudo systemctl enable seahub.service
 +</code>
 When the server is rebooted, Seafile will start automatically. When the server is rebooted, Seafile will start automatically.
  
 At this point, you have completed setting up the server, and can now test each of the services. At this point, you have completed setting up the server, and can now test each of the services.
-Step 7 — Testing File Syncing and Sharing Functionality+ 
 +***** Testing File Syncing and Sharing Functionality *****
  
 In this step, you will test the file synchronization and sharing functionality of the server you have set up and ensure they are working correctly. To do this, you will need to install the Seafile client program on a separate computer and/or a mobile device. In this step, you will test the file synchronization and sharing functionality of the server you have set up and ensure they are working correctly. To do this, you will need to install the Seafile client program on a separate computer and/or a mobile device.
Zeile 309: Zeile 312:
  
 Install and enable apache modules: Install and enable apache modules:
- +<code> 
-# Ubuntu +sudo a2enmod rewrite 
-sudo a2enmod rewrite +sudo a2enmod proxy_http 
-sudo a2enmod proxy_http +</code>
 Important: Due to the security advisory published by Django team, we recommend to disable GZip compression to mitigate BREACH attack. No version earlier than Apache 2.4 should be used. Important: Due to the security advisory published by Django team, we recommend to disable GZip compression to mitigate BREACH attack. No version earlier than Apache 2.4 should be used.
 Configuring Apache¶ Configuring Apache¶
  
 Modify Apache config file. For CentOS, this is vhost.conf. For Debian/Ubuntu, this is sites-enabled/000-default. Modify Apache config file. For CentOS, this is vhost.conf. For Debian/Ubuntu, this is sites-enabled/000-default.
 +<code>
 <VirtualHost *:80> <VirtualHost *:80>
     ServerName seafile.example.com     ServerName seafile.example.com
Zeile 349: Zeile 351:
     ProxyPassReverse / http://127.0.0.1:8000/     ProxyPassReverse / http://127.0.0.1:8000/
 </VirtualHost> </VirtualHost>
 +</code>
 Getting a Let's Encrypt certificate¶ Getting a Let's Encrypt certificate¶
  
Zeile 355: Zeile 357:
  
 First, go to the Certbot website and choose your web server and OS. First, go to the Certbot website and choose your web server and OS.
- 
-grafik 
- 
 Second, follow the detailed instructions then shown. Second, follow the detailed instructions then shown.
- 
-grafik 
  
 We recommend that you get just a certificate and that you modify the Apache configuration yourself: We recommend that you get just a certificate and that you modify the Apache configuration yourself:
 +<code>
 sudo certbot --apache certonly sudo certbot --apache certonly
 +</code>
 Follow the instructions on the screen. Follow the instructions on the screen.
  
Zeile 372: Zeile 369:
  
 To use HTTPS, you need to enable mod_ssl: To use HTTPS, you need to enable mod_ssl:
- +<code> 
-sudo a2enmod ssl +sudo a2enmod ssl 
 +</code>
 Then modify your Apache configuration file. Here is a sample: Then modify your Apache configuration file. Here is a sample:
 <code> <code>
Zeile 410: Zeile 407:
 </code> </code>
 Finally, make sure the virtual host file does not contain syntax errors and restart Apache for the configuration changes to take effect: Finally, make sure the virtual host file does not contain syntax errors and restart Apache for the configuration changes to take effect:
 +<code>
 sudo service apache2 restart sudo service apache2 restart
 +</code>
 Modifying ccnet.conf¶ Modifying ccnet.conf¶
  
Zeile 432: Zeile 429:
  
 Add the following line in the [fileserver] block on seafile.conf in /opt/seafile/conf: Add the following line in the [fileserver] block on seafile.conf in /opt/seafile/conf:
 +<code>
 host = 127.0.0.1  ## default port 0.0.0.0 host = 127.0.0.1  ## default port 0.0.0.0
 +</code>
 After his change, the file server only accepts requests from Apache. After his change, the file server only accepts requests from Apache.
 Starting Seafile and Seahub¶ Starting Seafile and Seahub¶
  
 Restart the seaf-server and Seahub for the config changes to take effect: Restart the seaf-server and Seahub for the config changes to take effect:
- +<code> 
-su seafile +su seafile 
-cd /opt/seafile/seafile-server-latest +cd /opt/seafile/seafile-server-latest 
-./seafile.sh restart +./seafile.sh restart 
-./seahub.sh restart +./seahub.sh restart 
- +</code>
wiki/seafile.1661092181.txt.gz · Zuletzt geändert: 2022/08/21 16:29 von mho

Falls nicht anders bezeichnet, ist der Inhalt dieses Wikis unter der folgenden Lizenz veröffentlicht: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki