Seafile Community Edition 12.0 Available for Testing! New Navigation and Viewing Experience, Enhanced SeaDoc Functions, New Knowledge Base and More

Hello, Seafile enthusiasts! We’re excited to announce that Seafile Community Edition 12.0 is open for testing. This version brings a host of improvements that will make your daily work more efficient and convenient, including a brand-new navigation experience, enhanced image viewing, and a fully upgraded SeaDoc, now at version 1.0, among other great features.

Let’s dive into the details.

1. Fresh Navigation & View Experience

In this update, we’ve given the navigation structure a complete makeover. The “My Libraries,” “Shared with Me,” and “Group Libraries” options have been combined into a single “Files” navigation item. This change allows you to see all your libraries on one page, significantly simplifying library management.

The sidebar can now be collapsed or expanded, and its width can be manually adjusted to suit your preferences.

Grid view presents files and data in a more intuitive and efficient manner, helping you find what you need faster and boosting your productivity.

2. File Details Sidebar: Information at a Glance

Click on the “Properties Details” icon in the toolbar to bring up the file details sidebar. This sidebar presents file information, such as size, last modified by, and modification time, in a more visually appealing way. It gives users a more comprehensive understanding of the file, enhancing their grasp of file attributes and improving operational efficiency.

3. UI Modernization – File Preview and Thumbnails

The image viewing experience and others have been upgraded to meet the diverse needs of users.

• Support rotate, download, delete, view raw image from image preview UI

• Support preview and generating thumbnails for HEIC format

• Support generating thumbnails for PDF files and videos

• Open Markdown files in a pop-up window instead of a new tab

• Unified the look and feel of toolbars for the viewer/editor for various file types (e.g.pdf, markdown, txt)

4. UI Modernization – Trash Bin and Library History

Trash bin and library history are now shown in a pop-up dialog.

5. Bulk Operations for Library Sharing

We’ve added bulk operation support for shared and upload links. This change not only increases operational efficiency but also makes library management more organized. Additionally, we display more information, such as the number of times each link has been accessed and the avatar of the creator, giving users a clearer picture of how their links are being used.

6. Enhanced SeaDoc functions

As one of Seafile’s core functions, SeaDoc has also been comprehensively enhanced in this update. In general, SeaDoc has been upgraded to version 1.0. It has optimized interfaces, a shortcut link function, export and collaboration capabilities, and enhanced table functions.

7. New wiki function: Create an efficient knowledge base

To meet users’ needs for knowledge management, we have added a wiki function based on the SeaDoc editor. Users can now create and manage a knowledge base for easy team information sharing and collaborative editing. This function not only improves team collaboration efficiency but also realizes efficient knowledge management and access.

Conclusion

Seafile Community Edition 12.0 is now open for testing. Come give it a try and let us know what you think! Your input is crucial to us, and we welcome your feedback to help us continuously improve our product. Let’s work together to make Seafile even better!

3 Likes

Github repo has only amd64 image. Will there be arm64 image provided to test?

arm64 image will only be released when the final version is ready.

*** Running /etc/my_init.d/01_create_data_links.sh...
*** Booting runit daemon...
*** Runit started as PID 20
*** Running /scripts/enterpoint.sh...
2024-11-23 14:35:26 Nginx ready
2024-11-23 14:35:26 This is an idle script (infinite loop) to keep container running.
[2024-11-23 14:35:26] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.

Error: .env file not found.
Please follow the upgrade manual to set the .env file.

Traceback (most recent call last):
  File "/scripts/start.py", line 94, in <module>
    main()
  File "/scripts/start.py", line 79, in main
    call('{} start'.format(get_script('seafile.sh')))
  File "/scripts/utils.py", line 70, in call
    return subprocess.check_call(*a, **kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-12.0.4/seafile.sh start' returned non-zero exit status 255.

Is there any way to specify that Seafile 12 runs via HTTPS through an external TLS termination?

I have Nginx set up on another VM which handles all of my external traffic for various web services and forwards traffic to Seafile. In my .env file, I have SEAFILE_SERVER_HOSTNAME set to the Nginx host’s FQDN, and SEAFILE_SERVER_PROTOCOL set to http because if I set it to https, I get infinitely redirected.

However, I’m seeing that a lot of the URLs in Seafile are using HTTP (such as user avatars), even though I have SERVICE_URL, FILE_SERVER_ROOT, and WEBDAV_URL (which doesn’t seem to do anything) set to the HTTPS link. I also had to add CSRF_TRUSTED_ORIGINS with the HTTPS link and set OAUTH_ENABLE_INSECURE_TRANSPORT to True in order to be able to log in successfully, so clearly the SEAFILE_SERVER_PROTOCOL value is overriding a number of values in different places.

I’m also seeing uploads fail because of this, as they’re trying to send data to the HTTP link, but I have my Nginx proxy redirecting to HTTPS. But when clients try to use the HTTPS link, Seafile redirects them again.

1 Like

SEAFILE_SERVER_PROTOCOL should be https, because it is the final protocol used by the browser to access your seafile.

We will write a document about how to use your own external reverse proxy instead of caddy.

2 Likes

Oh, fantastic. Thank you!

I ended up removing Caddy from the set of files included by docker compose and exposing port 80 from the Seafile YAML file, and that seems to have done the trick once I set SEAFILE_SERVER_PROTOCOL to https. I’m not sure whether that’s the recommended way, but it seems to be working for me so far.

However, I found another issue. When I try to create a library via the system admin area and then going to Libraries and clicking “+ New Library” at the top, if I select a user to assign ownership of the library to, I get an error that says “User undefined not found.” and the library isn’t created.

If I leave the owner field empty, however, it successfully creates the library and assigns ownership of it to the current user.

All I’m seeing in the logs when receiving the error from this (when the user field is populated) is in seahub.log, where I’m getting this:

2024-11-25 10:03:50,358 [WARNING] django.request:241 log_response Not Found: /api/v2.1/admin/libraries/

What does this error mean? There is no mention in any upgrade manual of an .env file.

Error: .env file not found.
Please follow the upgrade manual to set the .env file.

1 Like

When creating a link to provide external access to a file, there’s the option to send it to specific e-mail addresses. However, if the library is using list view (instead of icon view), then when typing the @ symbol, it’s triggering the Shift+2 shortcut to switch into icon view and dismissing the share dialog.

Thank you very much to report the two issues. We will fix them soon.

1 Like