Seafile ... What Synology Drive could have been

[Telos]

I wanted to get Seafile running on Docker. There's a docker-compose template available here.

With only a path change, and a few minor strikeouts, I came up with this unoriginal docker-compose...

version: '2.0'
services:
  db:
    image: mariadb:10.5
    container_name: seafile-mysql
    environment:
      - MYSQL_ROOT_PASSWORD=db_dev  # Requested, set the root's password of MySQL service.
      - MYSQL_LOG_CONSOLE=true
    volumes:
      - /volume1/docker/seafile/mysql:/var/lib/mysql  # Requested, specifies the path to MySQL data persistent store.
    networks:
      - seafile-net

  memcached:
    image: memcached:1.6
    container_name: seafile-memcached
    entrypoint: memcached -m 256
    networks:
      - seafile-net
       
  seafile:
    image: seafileltd/seafile-mc:latest
    container_name: seafile
    ports:
      - "8821:80"
#     - "443:443"  # If https is enabled, cancel the comment.
    volumes:
      - /volume1/docker/seafile/data:/shared   # Requested, specifies the path to Seafile data persistent store.
    environment:
      - DB_HOST=db
      - DB_ROOT_PASSWD=db_dev  # Requested, the value shuold be root's password of MySQL service.
      - TIME_ZONE=Etc/UTC  # Optional, default is UTC. Should be uncomment and set to your local time zone.
#      - [email protected] # Specifies Seafile admin user, default is '[email protected]'.
#     - SEAFILE_ADMIN_PASSWORD=asecret     # Specifies Seafile admin password, default is 'asecret'.
#      - SEAFILE_SERVER_LETSENCRYPT=false   # Whether to use https or not.
#      - SEAFILE_SERVER_HOSTNAME=docs.seafile.com # Specifies your host name if https is enabled.
    depends_on:
      - db
      - memcached
    networks:
      - seafile-net

networks:
  seafile-net:

After starting (via Portainer Stacks), I get 502 Bad Gateway... Following this video...

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

I noticed that the URL for my three containers is 192.168.14.x... compared to the video (and my other containers) which follow a 172.17.0.x IP.

I'm puzzled. This should be dirt simple. Or do any of the docker-compose elements fall outside the Synology "docker-compose" capabilities?

Thanks!

UPDATE 1:
Holy Moley... I just clicked again and it ran? Wow. Maybe I didn't wait long enough.

I till don't understand why the container IP range changed as it did, but all seems fine now. If this works out, I'll pull together a write-up.

FWIW, I began to look for alternatives to NextCloud, because, frankly for my needs, it is a bit bloated. I'd rather use the "best of the best" packages for my day-to-day needs. Hopefully Seafile answers my alternative "Dropbox" objective.

 

[Telos]

After several hours of putzing about with Seafile, I've grown quite content. Lightweight and fast in comparison to Synology Drive server. Supports sync on demand, pinning, multi-user, file encryption, versioning, user/group management... More capabilities here.

Did I mention it's open source?

Cross-platform... All you iOS user waiting for Synology's alpha release, wait no longer.

Shared video links enabled streaming (unlike Synology which forces download).

You can custom tailor the interface, so there is no brand shilling as Synology does with it's shared links.

First impressions are nice. Goodbye, Dropbox, Google Drive, One Drive, Synology Drive...

My only "miss", so far, is search (their paid service includes that). But that's pretty limited in Synology Drive, as I recall.

It does not offer PC backup, like Synology Drive. However, Synology Drive backup is horrid, and much better handled with PC tools such as File History, Macrium Reflect Free, Veeam, and so on.

Spin it up and judge for yourself

 

[one-eyed-king]

The only thing left is that you create a tutorial in the ressource section

But this time wrapped in a CODE block instead of ICODE block to retain the indention of the compose file

 

[Telos]

But this time wrapped in a CODE block instead of ICODE block

OK... fixed it for ya!