Cloudron Forum

[1.46.4] Update BookStack to 25.12.5 Full Changelog This release specifically addresses folder permission issues (often showing as an error when attempting to access content) which could occur from changes introduced in v25.12.4. Updated filter caching folder handling to avoid server filesystem permission issues. (#​6023) Added new option for more granular page filter control. Updated page content filtering to detect extra cases, and to apply a more aggressive allow-list style filter.

[1.49.0] Update chatwoot to 4.11.0 Full Changelog This release focuses on improving how conversations are handled and resolved inside Chatwoot. We are introducing structured resolution workflows, better AI assistance in the reply composer, and UX improvements that reduce friction for agents. We've improved the editor with Captain AI and a better experience for AI-assisted responses. AI reply suggestions now use related FAQs to improve response quality Agents can now: Improve reply, Change tone, Fix grammar and spelling, Suggest a reply, Summarize the conversation, Ask Copilot All of this works directly inside the composer. The agent can review and edit everything before sending.

[1.12.0] Update leantime to 3.7.0 Full Changelog TinyMCE removed all rich text editing now uses Tiptap. Existing content renders without changes, but any custom TinyMCE plugins or editor extensions will need to be rewritten for the Tiptap API. Group by Parent Task new grouping option in To-Do views with root parent resolution for ticket hierarchy Comment Reactions HTMX-based emoji reactions on comments (like, love, celebrate, funny, etc.) Strategy module relabeled to mission-driven language Fixed idea board internationalization issues Fixed goal KPI progress calculation Fixed milestone collapse behavior Fixed calendar duplicate events Fixed editor toolbar and border-radius inconsistencies Fixed slash menu viewport positioning at screen edges

@james Using Bitwarden means keeping your secret on a potentially compromised device. Better to use a hardware key. The problem with both Yubikey and Nitrokey is that if you lose the device, you lose the key. Big problem. The fact you cannot recover a passkey, make those devices a pass, from us. Or at least, they must be used in a far more careful and limited fashion - ie, fallback to email recovery - than what would otherwise be the case (sovereign recovery). With Trezor - and other hardware wallets that use deterministic webAuthN - you can recover from a seed. This means that the loss of a device is not catastrophic. EDIT: Am reading the Trezor forums and apparently they do support Passkeys, it's just that the Resident Key is encrypted with the seed, and not deterministically generated. So for recovery, you just back up the file using regular cloud storage. Looking forward to testing it on cloudron, and letting you all know the results. https://trezor.io/guides/bonus-tools/what-is-fido2