v0.2.27

Doca 0.2.27 — Browser-free rendering and single-file installation

简体中文

Rich-text and Markdown PDF exports now use pinned WeasyPrint 70.0. Canvas PNG exports use the official Canvas SDK's SVG output, isolated Node rendering and resvg. The runtime image no longer contains Chromium or Playwright and no longer requires a host seccomp JSON file or browser shared-memory configuration. LibreOffice remains for Office conversion; PDF.js remains for PDF reading and editable import.

Fresh SQLite/local-storage installations can download doca-compose-v0.2.27.yaml from this Release, save it as compose.yaml, set DOCA_ORIGIN and a newly generated DOCA_CREDENTIAL_MASTER_KEY, protect the file, and run docker compose up -d. Initialize the administrator with docker compose exec doca bash docker/admin.sh bootstrap. See deployment instructions for proxy, health, password reset and offline image delivery. The image includes the administrator scripts; no source checkout or companion seccomp file is needed.

Upgrade requirement: remove DOCA_PDF_CHROMIUM from the container environment, even if it is empty. This obsolete setting is explicitly rejected at startup and PDF export; there is no fallback to Chromium. Remove the old security_opt seccomp-file entry from your deployment configuration when using the new image. Existing sites must retain their Compose project name, persistent volumes, databases, attachments, configuration and credential master key. The standalone YAML is for fresh installations, not a replacement for an existing site's configuration.

Existing PDF endpoints, document formats, public editor APIs and historical SDK readers retain their established paths. No database structure or persisted-data conversion is introduced. To roll back, restore the previous code, dependency lock, image and matching deployment configuration while preserving all subsequent data. Upgrades from versions before 0.2.24 must also follow the 0.2.24 requirements.

Export fixes cover table column widths, Chinese font loading and HTML labels in diagrams. Diagrams containing SVG foreignObject are rasterized in the exporting client to preserve their labels; ordinary document text remains selectable. PDF import still approximates complex editable layouts. See the renderer verification for tested examples and limits.

GitHub Release assets and native Linux amd64/arm64 Docker Hub images are the publication targets. Publishing them does not update a running Doca site.

Web assets are attached as doca-web-assets-v0.2.27.tar.gz.
Extract it and publish the assets directory unchanged.
Set DOCA_ASSET_BASE to the HTTPS prefix that contains that assets directory, with no trailing slash.

Fresh installations can use the attached doca-compose-v0.2.27.yaml: edit the origin and generated master key, then run docker compose up -d. Administrator initialization is built into the image. A SHA-256 checksum is attached. Existing installations must preserve their project, volumes and key.

Image-only deployment files and initialization instructions are attached as doca-deploy-v0.2.27.tar.gz with a SHA-256 checksum.
Transfer this bundle to servers without GitHub access; no source checkout is needed.
The container image is separate. Pull the matching smartdoca/doca image or transfer it with docker save/load.