🚀 使用 Docker Compose 部署 Collabora（在线办公协作套件）

🚀 使用 Docker Compose 部署 Collabora Online

本文将详细介绍如何使用 Docker Compose 部署 Collabora Online——一个功能强大的开源在线办公套件，它可以与 Nextcloud 等应用集成，实现文档的在线编辑和协作。

📝 项目简介

Collabora Online 是一款基于 LibreOffice 技术的开源在线办公套件，支持多人实时协作编辑文档、电子表格和演示文稿。它通过浏览器提供与 Microsoft Office 和 LibreOffice 高度兼容的编辑体验。

核心特点：

• 多格式支持：支持 DOCX、XLSX、PPTX、ODT 等多种文档格式
• 实时协作：多用户可同时编辑同一文档，实时查看彼此更改
• 自托管部署：支持私有化部署，保障数据安全和控制权
• 移动端适配：响应式设计，支持平板和手机等移动设备
• 集成简便：可与 Nextcloud、OwnCloud 等主流网盘系统无缝集成

🔧 部署前准备

系统环境要求

• 操作系统：Linux（推荐 Ubuntu 20.04+ 或 CentOS 8+）
• Docker 引擎：版本 20.10+
• Docker Compose：版本 2.0+
• 硬件资源：
• 内存：至少 4GB（推荐 8GB+）
• 存储空间：至少 20GB 可用空间
• CPU：2 核心以上

环境检查

1. 检查 Docker 服务状态 bash systemctl status docker 确保 Docker 服务处于 active (running) 状态

2. 检查 Docker 版本 bash docker --version

3. 创建部署目录

   mkdir -p /home/compose/collabora && cd /home/compose/collabora

⚙️ 配置 Docker Compose

准备配置文件

创建 docker-compose.yml 文件：

#version: '3.8'
#version: "3"


services:
  collabora:
    image: collabora/code:6.4.14.3  # 固定使用 6.4.14.3 版本，稳定可靠
    container_name: collabora  # 容器名称，便于管理
    hostname: collabora  # 容器主机名，内部通信标识
    #healthcheck:
      #test: ['CMD','true'] #disable the healthcheck 强制测试通过
    environment:
      #- STGUIADDRESS=0.0.0.0:28384 #docker只能使用这方式修改GUI端口
    #1000为默认用户可能读取不到其他docker目录,设置0为管理员
      #- PUID=0
      #- PGID=0
      #- domain=192\\.168\\.0\\.19:801
      #https://1.1.1.1:20012/
      #- domain=1\\.1\\.1\\.1:20012
      # 关键！允许访问 Collabora 的域名/IP（需转义特殊字符，如点“.”用“\\.”，端口用“:”）
      # 示例：若与 Nextcloud 集成，Nextcloud 地址为 http://192.168.0.100:8080，则配置为 192\\.168\\.0\\.100:8080
      - domain=   # 必须填写！否则无法通过外部访问（格式：IP或域名，点需转义）
      - username=admin  # 管理员账号（登录管理界面用）
      - password=123456  # 管理员密码（建议修改为强密码，如 Admin@2024!）
      - dictionaries='de en es zh'  # 预装字典（德语、英语、西班牙语、中文）
    cap_add:
      - MKNOD  # 必要权限，用于创建特殊文件，确保文档处理正常（不可删除）
    volumes:
      #- ./syncthing:/var/syncthing
      #- ./collabora/coolwsd.xml:/etc/coolwsd/coolwsd.xml
      # 挂载自定义配置文件（若无需自定义，可注释此行，使用默认配置）
      - ./loolwsd/loolwsd1.xml:/etc/loolwsd/loolwsd.xml


      #- ./myfiles:/var/syncthing/myfiles
      #- /root/docker/自定义目录/:/自定义目录/
    ports:
     - '9980:9980'  # 端口映射：主机 9980 → 容器 9980（Collabora 核心端口）
    #network_mode: "host"    #主机模式.无需预先映射端口
    restart: always  # 容器退出后自动重启，保障服务稳定

关键配置说明

1. 镜像选择：使用 collabora/code:6.4.14.3 稳定版本镜像

2. 域名配置：domain 参数需设置为您的 Nextcloud 域名

3. 格式：your-nextcloud-domain.com

4. 如需转义特殊字符，使用双反斜杠：your\\.domain\\.com

5. 认证配置：

6. username 和 password：设置 Collabora 管理凭据

7. 建议使用强密码替代默认密码

8. 语言支持：dictionaries 参数配置词典语言

9. 支持德语(de)、英语(en)、西班牙语(es)、中文(zh)等

10. 端口映射：9980:9980 将容器内的 9980 端口映射到宿主机

11. 权限配置：cap_add: MKNOD 赋予容器创建设备节点的权限

在'/home/compose/collabora/loolwsd'目录下 创建 loolwsd1.xml 文件：

<!-- -*- nxml-child-indent: 4; tab-width: 4; indent-tabs-mode: nil -*- -->
<config>

    <!-- For more detailed documentation on typical configuration options please see:
         https://sdk.collaboraonline.com/docs/installation/Configuration.html -->

    <!-- Note: 'default' attributes are used to document a setting's default value as well as to use as fallback. -->
    <!-- Note: When adding a new entry, a default must be set in WSD in case the entry is missing upon deployment. -->

    <allowed_languages desc="List of supported languages of Writing Aids (spell checker, grammar checker, thesaurus, hyphenation) on this instance. Allowing too many has negative effect on startup performance." default="de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru">de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru</allowed_languages>

    <sys_template_path desc="Path to a template tree with shared libraries etc to be used as source for chroot jails for child processes." type="path" relative="true" default="systemplate"></sys_template_path>
    <child_root_path desc="Path to the directory under which the chroot jails for the child processes will be created. Should be on the same file system as systemplate and lotemplate. Must be an empty directory." type="path" relative="true" default="jails"></child_root_path>
    <mount_jail_tree desc="Controls whether the systemplate and lotemplate contents are mounted or not, which is much faster than the default of linking/copying each file." type="bool" default="true"></mount_jail_tree>

    <server_name desc="External hostname:port of the server running loolwsd. If empty, it's derived from the request (please set it if this doesn't work). Must be specified when behind a reverse-proxy or when the hostname is not reachable directly." type="string" default=""></server_name>
    <file_server_root_path desc="Path to the directory that should be considered root for the file server. This should be the directory containing loleaflet." type="path" relative="true" default="loleaflet/../"></file_server_root_path>
    <hexify_embedded_urls desc="Enable to protect encoded URLs from getting decoded by intermediate hops. Particularly useful on Azure deployments" type="bool" default="false"></hexify_embedded_urls>

    <memproportion desc="The maximum percentage of system memory consumed by all of the Collabora Online Development Edition, after which we start cleaning up idle documents" type="double" default="80.0"></memproportion>
    <num_prespawn_children desc="Number of child processes to keep started in advance and waiting for new clients." type="uint" default="1">1</num_prespawn_children>
    <per_document desc="Document-specific settings, including LO Core settings.">
        <max_concurrency desc="The maximum number of threads to use while processing a document." type="uint" default="4">4</max_concurrency>
        <batch_priority desc="A (lower) priority for use by batch eg. convert-to processes to avoid starving interactive ones" type="uint" default="5">5</batch_priority>
        <document_signing_url desc="The endpoint URL of signing server, if empty the document signing is disabled" type="string" default=""></document_signing_url>
        <redlining_as_comments desc="If true show red-lines as comments" type="bool" default="false">false</redlining_as_comments>
        <pdf_resolution_dpi desc="The resolution, in DPI, used to render PDF documents as image. Memory consumption grows proportionally. Must be a positive value less than 385. Defaults to 96." type="uint" default="96">96</pdf_resolution_dpi>
        <idle_timeout_secs desc="The maximum number of seconds before unloading an idle document. Defaults to 1 hour." type="uint" default="3600">3600</idle_timeout_secs>
        <!-- Idle save and auto save are checked every 30 seconds -->
        <!-- They are disabled when the value is zero or negative. -->
        <idlesave_duration_secs desc="The number of idle seconds after which document, if modified, should be saved. Defaults to 30 seconds." type="int" default="30">30</idlesave_duration_secs>
        <autosave_duration_secs desc="The number of seconds after which document, if modified, should be saved. Defaults to 5 minutes." type="int" default="300">300</autosave_duration_secs>
        <always_save_on_exit desc="On exiting the last editor, always perform the save, even if the document is not modified." type="bool" default="false">false</always_save_on_exit>
        <limit_virt_mem_mb desc="The maximum virtual memory allowed to each document process. 0 for unlimited." type="uint">0</limit_virt_mem_mb>
        <limit_stack_mem_kb desc="The maximum stack size allowed to each document process. 0 for unlimited." type="uint">8000</limit_stack_mem_kb>
        <limit_file_size_mb desc="The maximum file size allowed to each document process to write. 0 for unlimited." type="uint">0</limit_file_size_mb>
        <limit_num_open_files desc="The maximum number of files allowed to each document process to open. 0 for unlimited." type="uint">0</limit_num_open_files>
        <limit_load_secs desc="Maximum number of seconds to wait for a document load to succeed. 0 for unlimited." type="uint" default="100">100</limit_load_secs>
        <limit_convert_secs desc="Maximum number of seconds to wait for a document conversion to succeed. 0 for unlimited." type="uint" default="100">100</limit_convert_secs>
        <cleanup desc="Checks for resource consuming (bad) documents and kills associated kit process. A document is considered resource consuming (bad) if is in idle state for idle_time_secs period and memory usage passed limit_dirty_mem_mb or CPU usage passed limit_cpu_per" enable="false">
            <cleanup_interval_ms desc="Interval between two checks" type="uint" default="10000">10000</cleanup_interval_ms>
            <bad_behavior_period_secs desc="Minimum time period for a document to be in bad state before associated kit process is killed. If in this period the condition for bad document is not met once then this period is reset" type="uint" default="60">60</bad_behavior_period_secs>
            <idle_time_secs desc="Minimum idle time for a document to be candidate for bad state" type="uint" default="300">300</idle_time_secs>
            <limit_dirty_mem_mb desc="Minimum memory usage for a document to be candidate for bad state" type="uint" default="3072">3072</limit_dirty_mem_mb>
            <limit_cpu_per desc="Minimum CPU usage for a document to be candidate for bad state" type="uint" default="85">85</limit_cpu_per>
            <lost_kit_grace_period_secs desc="The minimum grace period for a lost kit process (not referenced by loolwsd) to resolve its lost status before it is terminated. To disable the cleanup of lost kits use value 0" default="120">120</lost_kit_grace_period_secs>
        </cleanup>
    </per_document>

    <per_view desc="View-specific settings.">
        <out_of_focus_timeout_secs desc="The maximum number of seconds before dimming and stopping updates when the browser tab is no longer in focus. Defaults to 120 seconds." type="uint" default="120">120</out_of_focus_timeout_secs>
        <idle_timeout_secs desc="The maximum number of seconds before dimming and stopping updates when the user is no longer active (even if the browser is in focus). Defaults to 15 minutes." type="uint" default="900">900</idle_timeout_secs>
    </per_view>

    <loleaflet_html desc="Allows UI customization by replacing the single endpoint of loleaflet.html" type="string" default="loleaflet.html">loleaflet.html</loleaflet_html>
    <ver_suffix desc="Appended to etags to allow easy refresh of changed files during development" type="string" default=""></ver_suffix>

    <logging>
        <color type="bool">true</color>
        <level type="string" desc="Can be 0-8 (with the lowest numbers being the least verbose), or none (turns off logging), fatal, critical, error, warning, notice, information, debug, trace" default="warning">warning</level>
        <most_verbose_level_settable_from_client type="string" desc="A loggingleveloverride message from the client can not set a more verbose log level than this" default="notice">notice</most_verbose_level_settable_from_client>
        <least_verbose_level_settable_from_client type="string" desc="A loggingleveloverride message from a client can not set a less verbose log level than this" default="fatal">fatal</least_verbose_level_settable_from_client>
        <protocol type="bool" desc="Enable minimal client-site JS protocol logging from the start">false</protocol>
        <!-- lokit_sal_log example: Log WebDAV-related messages, that is interesting for debugging Insert - Image operation: "+TIMESTAMP+INFO.ucb.ucp.webdav+WARN.ucb.ucp.webdav"
             See also: https://docs.libreoffice.org/sal/html/sal_log.html -->
        <lokit_sal_log type="string" desc="Fine tune log messages from LOKit. Default is to suppress log messages from LOKit." default="-INFO-WARN">-INFO-WARN</lokit_sal_log>
        <file enable="false">
            <!-- If you use other path than /var/log and you run loolwsd from systemd, make sure that you enable that path in loolwsd.service (ReadWritePaths). -->
            <property name="path" desc="Log file path.">/var/log/loolwsd.log</property>
            <property name="rotation" desc="Log file rotation strategy. See Poco FileChannel.">never</property>
            <property name="archive" desc="Append either timestamp or number to the archived log filename.">timestamp</property>
            <property name="compress" desc="Enable/disable log file compression.">true</property>
            <property name="purgeAge" desc="The maximum age of log files to preserve. See Poco FileChannel.">10 days</property>
            <property name="purgeCount" desc="The maximum number of log archives to preserve. Use 'none' to disable purging. See Poco FileChannel.">10</property>
            <property name="rotateOnOpen" desc="Enable/disable log file rotation on opening.">true</property>
            <property name="flush" desc="Enable/disable flushing after logging each line. May harm performance. Note that without flushing after each line, the log lines from the different processes will not appear in chronological order.">false</property>
        </file>
        <anonymize>
            <anonymize_user_data type="bool" desc="Enable to anonymize/obfuscate of user-data in logs. If default is true, it was forced at compile-time and cannot be disabled." default="false">false</anonymize_user_data>
            <anonymization_salt type="uint" desc="The salt used to anonymize/obfuscate user-data in logs. Use a secret 64-bit random number." default="82589933">82589933</anonymization_salt>
        </anonymize>
    </logging>

    <trace_event desc="The possibility to turn on generation of a Chrome Trace Event file" enable="false">
        <path desc="Output path for the Trace Event file, to which they will be written if turned on at run-time" type="string" default="/var/log/loolwsd.trace.json">/var/log/loolwsd.trace.json</path>
    </trace_event>

    <loleaflet_logging desc="Logging in the browser console" default="false">false</loleaflet_logging>

    <trace desc="Dump commands and notifications for replay. When 'snapshot' is true, the source file is copied to the path first." enable="false">
        <path desc="Output path to hold trace file and docs. Use '%' for timestamp to avoid overwriting. For example: /some/path/to/looltrace-%.gz" compress="true" snapshot="false"></path>
        <filter>
            <message desc="Regex pattern of messages to exclude"></message>
        </filter>
        <outgoing>
            <record desc="Whether or not to record outgoing messages" default="false">false</record>
        </outgoing>
    </trace>

    <net desc="Network settings">
      <!-- On systems where localhost resolves to IPv6 [::1] address first, when net.proto is all and net.listen is loopback, loolwsd unexpectedly listens on [::1] only.
           You need to change net.proto to IPv4, if you want to use 127.0.0.1. -->
      <proto type="string" default="all" desc="Protocol to use IPv4, IPv6 or all for both">all</proto>
      <listen type="string" default="any" desc="Listen address that loolwsd binds to. Can be 'any' or 'loopback'.">any</listen>
      <!-- this allows you to shift all of our URLs into a sub-path from
           https://my.com/loleaflet/a123... to https://my.com/my/sub/path/loleaflet/a123... -->
      <service_root type="path" default="" desc="Prefix all the pages, websockets, etc. with this path."></service_root>
      <post_allow desc="Allow/deny client IP address for POST(REST)." allow="true">
        <host desc="The IPv4 private 192.168 block as plain IPv4 dotted decimal addresses.">192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
        <host desc="Ditto, but as IPv4-mapped IPv6 addresses">::ffff:192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
        <host desc="The IPv4 loopback (localhost) address.">127\.0\.0\.1</host>
        <host desc="Ditto, but as IPv4-mapped IPv6 address">::ffff:127\.0\.0\.1</host>
        <host desc="The IPv6 loopback (localhost) address.">::1</host>
        <host desc="The IPv4 private 172.17.0.0/16 subnet (Docker).">172\.17\.[0-9]{1,3}\.[0-9]{1,3}</host>
        <host desc="Ditto, but as IPv4-mapped IPv6 addresses">::ffff:172\.17\.[0-9]{1,3}\.[0-9]{1,3}</host>
      </post_allow>
      <frame_ancestors desc="Specify who is allowed to embed the LO Online iframe (loolwsd and WOPI host are always allowed). Separate multiple hosts by space."></frame_ancestors>
      <connection_timeout_secs desc="Specifies the connection, send, recv timeout in seconds for connections initiated by loolwsd (such as WOPI connections)." type="int" default="30"></connection_timeout_secs>

      <!-- this setting radically changes how online works, it should not be used in a production environment -->
      <proxy_prefix type="bool" default="false" desc="Enable a ProxyPrefix to be passed int through which to redirect requests"></proxy_prefix>
    </net>

    <ssl desc="SSL settings">
        <!-- switches from https:// + wss:// to http:// + ws:// -->
        <enable type="bool" desc="Controls whether SSL encryption between loolwsd and the network is enabled (do not disable for production deployment). If default is false, must first be compiled with SSL support to enable." default="false">true</enable>
        <!-- SSL off-load can be done in a proxy, if so disable SSL, and enable termination below in production -->
        <termination desc="Connection via proxy where loolwsd acts as working via https, but actually uses http." type="bool" default="true">false</termination>
        <cert_file_path desc="Path to the cert file" relative="false">/etc/loolwsd/cert.pem</cert_file_path>
        <key_file_path desc="Path to the key file" relative="false">/etc/loolwsd/key.pem</key_file_path>
        <ca_file_path desc="Path to the ca file" relative="false">/etc/loolwsd/ca-chain.cert.pem</ca_file_path>
        <cipher_list desc="List of OpenSSL ciphers to accept" default="ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH"></cipher_list>
        <hpkp desc="Enable HTTP Public key pinning" enable="false" report_only="false">
            <max_age desc="HPKP's max-age directive - time in seconds browser should remember the pins" enable="true">1000</max_age>
            <report_uri desc="HPKP's report-uri directive - pin validation failure are reported at this URL" enable="false"></report_uri>
            <pins desc="Base64 encoded SPKI fingerprints of keys to be pinned">
            <pin></pin>
            </pins>
        </hpkp>
    </ssl>

    <security desc="Altering these defaults potentially opens you to significant risk">
      <seccomp desc="Should we use the seccomp system call filtering." type="bool" default="true">true</seccomp>
      <capabilities desc="Should we require capabilities to isolate processes into chroot jails" type="bool" default="true">true</capabilities>
      <jwt_expiry_secs desc="Time in seconds before the Admin Console's JWT token expires" type="int" default="1800">1800</jwt_expiry_secs>
      <enable_macros_execution desc="Specifies whether the macro execution is enabled in general. This will enable Basic, Beanshell, Javascript and Python scripts. If it is set to false, the macro_security_level is ignored. If it is set to true, the mentioned entry specified the level of macro security." type="bool" default="false">false</enable_macros_execution>
      <macro_security_level desc="Level of Macro security. 1 (Medium) Confirmation required before executing macros from untrusted sources. 0 (Low, not recommended) All macros will be executed without confirmation." type="int" default="1">1</macro_security_level>
      <enable_metrics_unauthenticated desc="When enabled, the /lool/getMetrics endpoint will not require authentication." type="bool" default="false">false</enable_metrics_unauthenticated>
    </security>

    <watermark>
      <opacity desc="Opacity of on-screen watermark from 0.0 to 1.0" type="double" default="0.2"></opacity>
      <text desc="Watermark text to be displayed on the document if entered" type="string"></text>
    </watermark>

    <welcome>
      <enable type="bool" desc="Controls whether the welcome screen should be shown to the users on new install and updates." default="true">true</enable>
      <enable_button type="bool" desc="Controls whether the welcome screen should have an explanatory button instead of an X button to close the dialog." default="false">false</enable_button>
      <path desc="Path to 'welcome-$lang.html' files served on first start or when the version changes. When empty, defaults to the Release notes." type="path" relative="true" default="loleaflet/welcome"></path>
    </welcome>

    <user_interface>
      <mode type="string" desc="Controls the user interface style (classic|notebookbar)" default="classic">classic</mode>
    </user_interface>

    <storage desc="Backend storage">
        <filesystem allow="false" />
        <wopi desc="Allow/deny wopi storage. Mutually exclusive with webdav." allow="true">
            <host desc="Regex pattern of hostname to allow or deny." allow="true">.*</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">localhost</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">10\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.1[6789]\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.2[0-9]\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.3[01]\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="true">192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
            <host desc="Regex pattern of hostname to allow or deny." allow="false">192\.168\.1\.1</host>
            <max_file_size desc="Maximum document size in bytes to load. 0 for unlimited." type="uint">0</max_file_size>
            <reuse_cookies desc="When enabled, cookies from the browser will be captured and set on WOPI requests." type="bool" default="false">false</reuse_cookies>
            <locking desc="Locking settings">
                <refresh desc="How frequently we should re-acquire a lock with the storage server, in seconds (default 15 mins) or 0 for no refresh" type="int" default="900">900</refresh>
            </locking>
        </wopi>
        <ssl desc="SSL settings">
        <as_scheme type="bool" default="true" desc="When set we exclusively use the WOPI URI's scheme to enable SSL for storage">false</as_scheme>
            <enable type="bool" desc="If as_scheme is false or not set, this can be set to force SSL encryption between storage and loolwsd. When empty this defaults to following the ssl.enable setting"></enable>
            <cert_file_path desc="Path to the cert file" relative="false"></cert_file_path>
            <key_file_path desc="Path to the key file" relative="false"></key_file_path>
            <ca_file_path desc="Path to the ca file. If this is not empty, then SSL verification will be strict, otherwise cert of storage (WOPI-like host) will not be verified." relative="false"></ca_file_path>
            <cipher_list desc="List of OpenSSL ciphers to accept. If empty the defaults are used. These can be overriden only if absolutely needed."></cipher_list>
        </ssl>
    </storage>

    <tile_cache_persistent desc="Should the tiles persist between two editing sessions of the given document?" type="bool" default="true">true</tile_cache_persistent>

    <admin_console desc="Web admin console settings.">
        <enable desc="Enable the admin console functionality" type="bool" default="true">true</enable>
        <enable_pam desc="Enable admin user authentication with PAM" type="bool" default="false">false</enable_pam>
        <username desc="The username of the admin console. Ignored if PAM is enabled.">admin</username>
        <password desc="The password of the admin console. Deprecated on most platforms. Instead, use PAM or loolconfig to set up a secure password.">123456</password>
    </admin_console>

    <monitors desc="Addresses of servers we connect to on start for monitoring">
    </monitors>



</config>

🚀 启动与验证

启动服务

docker compose up -d

验证服务状态

1. 检查容器运行状态 bash docker ps 应该看到 collabora 容器处于 Up 状态

2. 查看服务日志 bash docker compose logs -f

3. 验证服务访问 bash curl http://localhost:9980 或通过浏览器访问 http://你的服务器IP:9980

（2）验证服务可用性

1. 访问健康检查接口：打开浏览器，输入 http://服务器IP:9980/healthcheck；
2. 若返回 OK，说明 Collabora 服务正常运行；
3. （可选）访问管理员界面：输入 http://服务器IP:9980/loleaflet/dist/admin/admin.html，使用配置的 username（admin）和 password（123456）登录，能成功登录即管理员功能正常。

---

🔌 基础配置与使用

与 Nextcloud 集成配置

1. 在 Nextcloud 中安装 Collabora Online 应用
2. 进入 Nextcloud 应用市场

3. 搜索并安装 "Collabora Online" 应用

4. 配置 Nextcloud 连接

5. 进入 Nextcloud 管理设置 → Collabora Online
6. 选择 "使用您自己的服务器"
7. 输入 Collabora 服务器地址：https://your-collabora-domain:9980
8. 保存配置

自定义配置文件

创建自定义配置文件以优化 Collabora 行为：

1.创建配置目录

   mkdir -p loolwsd

2.创建自定义配置文件 loolwsd/loolwsd.xml

   <config>
     <ssl enable="true" terminate="false"/>
     <storage desc="storage desc">
       <filesystem allow="true"/>
     </storage>
     <remote_config allow="true"/>
     <admin_console enable="true" username="admin"/>
   </config>

性能优化配置

根据服务器资源调整配置：

1.内存限制：在 docker-compose.yml 中添加资源限制

   deploy:
     resources:
       limits:
         memory: 4G
         cpus: '2.0'

2.文档处理限制：调整并发文档处理数量

---

🔌 基础配置与使用2

Collabora 通常需与云存储平台（如 Nextcloud）集成才能发挥作用，以下是核心使用步骤：

1. 与 Nextcloud 集成（最常用场景）

1. 在 Nextcloud 中安装 “Collabora Online” 应用：
   • 登录 Nextcloud → 应用市场 → 搜索 “Collabora Online” → 点击 “下载并启用”；
2. 配置 Collabora 服务器地址：
   • Nextcloud 管理员界面 → 设置 → Collabora Online → 输入 http://服务器IP:9980（或域名，如 https://collabora.example.com:9980）；
3. 验证集成：在 Nextcloud 中创建一个 .docx 或 .odt 文件，点击打开，若能进入在线编辑界面（带工具栏和实时保存按钮），说明集成成功。

2. 管理员界面操作（基础）

登录管理员界面（http://服务器IP:9980/loleaflet/dist/admin/admin.html）后，可进行以下操作：

• 查看状态：左侧 “Status” 查看服务运行状态、活跃会话、资源占用；
• 管理权限：“Access” 配置允许访问的域名（补充 domain 未覆盖的地址）；
• 日志查看：“Logs” 查看服务日志，排查编辑失败等问题。

3. 文档协作示例（多人实时编辑）

1. 在集成的 Nextcloud 中创建一个表格文件（.xlsx 或 .ods）；
2. 分享文件给其他用户（设置 “可编辑” 权限）；
3. 多个用户同时打开文件，修改内容（如输入文字、调整单元格），会实时看到对方的编辑状态（光标位置、修改内容），无需手动刷新。

---

🛠️ 维护与管理

日常维护操作

1.服务启停

   # 停止服务
   docker compose down

   # 启动服务
   docker compose up -d

2.数据备份

   # 备份配置文件
   tar -czf collabora-backup-$(date +%Y%m%d).tar.gz ./loolwsd

3.服务更新

   # 进入部署目录
   cd /home/compose/collabora

   # 拉取最新镜像
   docker compose pull

   # 重启服务
   docker compose down
   docker compose up -d

监控与日志

1.查看实时日志

   docker compose logs -f

2.监控资源使用

   docker stats collabora

3.检查服务健康状态

   docker exec collabora loolwsd --version

🐛 常见问题排查

1. 无法访问 Collabora 服务

问题现象：浏览器访问 http://IP:9980 无响应

解决方案： - 检查防火墙设置： bash # 开放 9980 端口 ufw allow 9980 - 验证容器状态：docker ps - 查看服务日志：docker compose logs

2. Nextcloud 无法连接 Collabora

问题现象：Nextcloud 中提示无法连接到 Collabora Online

解决方案： - 检查 domain 参数配置是否正确 - 验证域名解析是否正常 - 确认 SSL 证书配置（如使用 HTTPS）

3. 文档无法加载或编辑

问题现象：文档在 Collabora 中无法正常打开

解决方案： - 检查文件权限和所有权 - 验证内存资源是否充足 - 查看 Collabora 日志获取详细错误信息

4. 性能问题

问题现象：文档打开或保存缓慢

解决方案： - 增加容器内存限制 - 优化服务器网络配置 - 考虑使用 SSD 存储

通过本教程，您应该已经成功部署并配置了 Collabora Online 服务。Collabora 的强大功能和与 Nextcloud 的无缝集成，为您提供了完整的在线文档协作解决方案。如果在使用过程中遇到其他问题，可以参考 Collabora 官方文档或相关社区资源。

---

🐛 常见问题排查2

1. Nextcloud 无法连接 Collabora（提示 “无法联系 Collabora 服务器”）

• 原因 1：domain 配置错误（未包含 Nextcloud 的域名 / IP）。解决：修改 docker-compose.yml 中的 domain，确保包含 Nextcloud 的地址（如 Nextcloud 地址为 192.168.1.100:8080，则 domain=192\\.168\\.1\\.100:8080），重启容器。

• 原因 2：9980 端口未开放或服务器防火墙拦截。解决：重新开放 9980 端口（如 sudo ufw allow 9980/tcp），并在云服务器安全组中添加对应规则。

2. 文档编辑时卡顿或崩溃

• 原因 1：服务器内存不足（Collabora 处理大文件需较多内存）。

  解决：升级服务器内存（至少 4GB），或关闭不必要的服务释放内存； - 原因 2：Collabora 版本与 Nextcloud 不兼容。

  解决：确认 Nextcloud 版本与 Collabora 版本匹配（参考 官方兼容性列表），回退到兼容版本。

3. 管理员界面登录失败（提示 “用户名或密码错误”）

• 原因：username 或 password 配置错误，或未重启容器生效。

  解决：修改 docker-compose.yml 中的 username 和 password，执行 docker compose restart 后重新登录。

4. 挂载自定义配置文件后服务启动失败

• 原因：loolwsd1.xml 内容错误（格式错误或参数冲突）。

  解决：注释掉 volumes 中的配置文件挂载项（使用默认配置），重启容器；若需自定义，参考 官方默认配置 修正内容。

通过以上步骤，新手可快速部署 Collabora 在线办公套件，并与 Nextcloud 集成实现私有云协作。Collabora 适合团队内部文档协作、个人云办公场景，如需深入功能（如 SSL 加密、集群部署），可参考 Collabora 官方文档。