We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Running Seafiles Server
-
- Posts: 2
- Joined: Thu Nov 13, 2014 4:06 pm
Running Seafiles Server
Anybody out there running the seafiles Server with VestaCP (at best with https)?
I tried to add additional config files for nginx resp. apache but they are still ignored...
Thanks for any suggestion!
(btw. I'm using vesta on Debian 7)
best regards
I tried to add additional config files for nginx resp. apache but they are still ignored...
Thanks for any suggestion!
(btw. I'm using vesta on Debian 7)
best regards
-
- Posts: 2
- Joined: Thu Nov 13, 2014 4:06 pm
Re: Running Seafiles Server
Finaly I got it working...
Maybe anybody wants to solve the same problem, so here is my workaround:
I added two new templates to /usr/local/vesta/data/templates/web/apache2/
seafile.tpl and seafile.stpl. Therfore I took a copy of default.(s)tpl and modyfied it like Seafiles documentation describes and got something like
for the .stpl.
Then I insalled seafiles in a sea folder in /home/<user>/web/<domain>/sea
After creating the new domain in Vesta with default-template, I changed the template to seafiles.
The tricky as well as ugly part was to add following line at the end of /etc/apache2/apache2.conf
After (configuring and) starting seafiles and seahub everything worked.
Where could the parameter of the FastCGIExternalServer be placed better?
How could the hard coded domain name and user be avoided?
Any Ideas?
best regards
Maybe anybody wants to solve the same problem, so here is my workaround:
I added two new templates to /usr/local/vesta/data/templates/web/apache2/
seafile.tpl and seafile.stpl. Therfore I took a copy of default.(s)tpl and modyfied it like Seafiles documentation describes and got something like
Code: Select all
<VirtualHost %ip%:%web_ssl_port%>
ServerName %domain_idn%
%alias_string%
ServerAdmin %email%
DocumentRoot %sdocroot%
Alias /media %home%/%user%/web/%domain%/sea/seafile-server-latest/seahub/media
Alias /vstats/ %home%/%user%/web/%domain%/stats/
Alias /error/ %home%/%user%/web/%domain%/document_errors/
CustomLog /var/log/%web_system%/domains/%domain%.bytes bytes
CustomLog /var/log/%web_system%/domains/%domain%.log combined
ErrorLog /var/log/%web_system%/domains/%domain%.error.log
<Directory %sdocroot%>
AllowOverride All
SSLRequireSSL
Options +Includes -Indexes +ExecCGI
</Directory>
<Directory %home%/%user%/web/%domain%/stats>
AllowOverride All
</Directory>
SSLEngine on
SSLVerifyClient none
SSLCertificateFile %ssl_crt%
SSLCertificateKeyFile %ssl_key%
%ssl_ca_str%SSLCertificateChainFile %ssl_ca%
RewriteEngine On
<Location /media>
Order allow,deny
Allow from all
</Location>
#
# seafile fileserver
#
ProxyPass /seafhttp http://127.0.0.1:8082
ProxyPassReverse /seafhttp http://127.0.0.1:8082
RewriteRule ^/seafhttp - [QSA,L]
#
# seahub
#
RewriteRule ^/(media.*)$ /$1 [QSA,L,PT]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ /seahub.fcgi/$1 [QSA,L,E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
<IfModule mod_ruid2.c>
RMode config
RUidGid %user% %group%
RGroups www-data
</IfModule>
<IfModule itk.c>
AssignUserID %user% %group%
</IfModule>
Include %home%/%user%/conf/web/s%web_system%.%domain%.conf*
</VirtualHost>
Then I insalled seafiles in a sea folder in /home/<user>/web/<domain>/sea
After creating the new domain in Vesta with default-template, I changed the template to seafiles.
The tricky as well as ugly part was to add following line at the end of /etc/apache2/apache2.conf
Code: Select all
FastCGIExternalServer /home/<user>/web/<domain>/public_html/seahub.fcgi -host 127.0.0.1:8000
Where could the parameter of the FastCGIExternalServer be placed better?
How could the hard coded domain name and user be avoided?
Any Ideas?
best regards
Re: Running Seafiles Server
Hello BlueCasket,
did you since installed SeaFile again?
Right now i am strugeling to get it running in my subdomain.domain.com
Could you be a bit more verbose on the part:
"Then I insalled seafiles in a sea folder in /home/<user>/web/<domain>/sea"
I guess you also had to clear the ports in the vesta firewall settings for 8000 and 8082?
Thanks a lot!
did you since installed SeaFile again?
Right now i am strugeling to get it running in my subdomain.domain.com
Could you be a bit more verbose on the part:
"Then I insalled seafiles in a sea folder in /home/<user>/web/<domain>/sea"
I guess you also had to clear the ports in the vesta firewall settings for 8000 and 8082?
Thanks a lot!