Server setup nightmares for new users

I was able to successfully do the following without any issues:

/manual.seafile.com/deploy/using_sqlite.html

I admit I’m not terribly familiar with Linux. But things become really poorly documented after this point in terms of getting HTTPS to work.

What I can’t understand is, if I follow the steps in the above URL, then where does this fit in?

/manual.seafile.com/deploy/deploy_with_apache.html

Right off the bat, a2enmod doesn’t work. And I know apache2 isn’t installed. But if I followed the first URL, 1. what exact http server is actually being used? Nginx? Apache? It’s own rolled version? Can I access its configs to do SSL?

So say I install apache2, which I attempted, I finally have access to a2enmod. But then the documentation goes on to say the following:

Modify Apache config file: (sites-enabled/000-default) for ubuntu/debian, (vhost.conf) for centos/fedora

Where is sites-eanbled? Why is there not even a simple example location to assist new users?

So by writing this message, it finally clicks, that seahub will only run on 8082, and that you’re basically using Apache/Nginx to proxy into it. It would likely help a lot of new users to have this detail explained in the “Deploying Seafile with *” and the “Config Seahub with *” articles. Quite literally, had no idea this is how it worked.

So given that, to reduce overhead, is there no way to make seahub work with SSL without having to wrap another daemon around it?

1 Like

Use the community manual. Should work right away.
And you need a reverse proxy for SSL.

I got it to work. I’m just asking if there’s a way around using proxies for SSL, and wondering if we, or I, can improve the documentation. I’m a developer of more than 20 years, and my input could be useful to others.

you have to use a reverse proxy for SSL, Seahub itself just offers a http port.

There is a community for which you could contribute