Summary

Dnote server v3.0.0 makes self-hosting simpler with a smaller resource footprint. By switching to SQLite, you no longer need to run a separate PostgreSQL database server. The entire setup now runs as a single binary with a single database file. Docker images are now available for Linux AMD64, ARM64, ARMv7, and 386. Run Dnote on Raspberry Pi, ARM servers, and other platforms. The server also officially supports FreeBSD AMD64, expanding deployment options for BSD users.

User management is now built into the server CLI with the dnote-server user subcommand for creating, removing, and managing users. Docker healthcheck support improves container orchestration. Client rate limiting helps prevent server overload. Also, in keeping with Dnote’s guiding principle of openness, Dnote is now licensed under more permissive Apache 2.0.

What's Changed

• Use SQLite on the server (#681)
• Run server on port 3001 (#687)
• Remove email verification (#688)
• Rate limit API (#689)
• Manage users with server CLI (#696)
• Converge if using same book names while syncing (#694)
• Add Docker images for linux arm64, armv7, 386 (#697)
• Specify DBPath for docker (#699)
• Remove public from CLI (#703)
• Remove unused templates (#702)
• Remove the unused encrypted and public fields (#700)
• Merge user and account (#701)
• Improve empty server sync when multiple clients exist (#706)
• Fix an edge case of repeated syncs due to orphaned note (#704)
• Auto vacuum and manage connections (#705)
• Use Apache 2.0 license (#708)
• Simplify email backend and remove --appEnv (#710)
• Rename webUrl to baseUrl (#711)
• Fix log level (#712)

Migration Guide

Database Change: Database Migration Required. Server 3.0 uses SQLite instead of PostgreSQL. To migrate your existing data from PostgreSQL to SQLite, see https://github.com/dnote/pg2sqlite.

Configuration change: Please see the README for the new server configuration.