Have set up seafile docker according to /docker/pro-edition/deploy_seafile_pro_with_docker/
I have found a few issues that require manual intervention to get seafile to work.
Here is the process I am using.
- docker-compose up -d
- Despite 443 being unhashed in docker-compose there is issues getting the acme challenge to work so I need to modify the nginx config to include “location ~/.well-known/acme-challenge/ {
root /var/www/;
}” - manually generate ssl is generated by /scripts/ssl.sh /shared/ssl/ domain
- add the following lines to the nginx config"
listen 443 ssl;
ssl_certificate /shared/ssl/domain/fullchain.cer
ssl_certificate_key /shared/ssl/domain/domain.key" - then I need to run through the scripts at opt/seafile/seafile-proserver10.0.4/setup-seafile-mysql.sh to create or once initially created connect to existing DB.
- Then I need to run seahub.sh and seafile.sh start.
I feel like this latest version has been packaged incorrectly or I am clearly missing something here in order to have to do all these manual steps.
As its on docker, I don’t want to make these changes as they will not persist if I run a docker-compose down.
I know this version is relatively new is anyone else experiencing this issue. I will look at replicating this on a totally new machine although I’ve done a few complete rebuilds and am continuing to get the same result.
I have also noticed that when I run tree directory it does not match what is found in the guide, I assume this is an issue due to the deployment failing at the acme-challenge verification phase