Did you read the docs above?
Use the .env file
Did you read the docs above?
Use the .env file
It's for plugging in an external LLM via those variables, as in API URL and API KEY
https://github.com/tidwall/pogocache
Fast caching software built from scratch with a focus on low latency and cpu efficency.
https://pogocache.com
Faster: Pogocache is faster than Memcache, Valkey, Redis, Dragonfly, and Garnet. It has the lowest latency per request, providing the quickest response times. It's optimized to scale from one to many cores, giving you the best single-threaded and multithreaded performance.
Cheaper: Pogocache uses the fewest cpu cycles per request; minimizing server load, energy usage, and the overall cost to operate.
Easier: Pogocache runs as a server-based program. It supports Memcache, Valkey/Redis, HTTP, and Postgres wire protocols, allowing for the use of system tools such as curl and psql, and numerous client libraries that are available for most programming languages.
Embeddable: Optionally instead of running Pogocache as a server-based program, the self-contained pogocache.c file can be compiled into existing software, bypassing the network and directly accessing the cache programmatically. Running embedded provides raw speed, with over 100M ops per second.
--
From the guy who built many iconic DBs.
Usable for Cloudron 10?
This may begin to displace n8n
https://github.com/mindroom-ai/mindroom
AI agents that live in your chat rooms.
MindRoom is an open-source multi-agent runtime built on Matrix that works with nearly any cloud or local AI model.
You define agents in a YAML file or in the web dashboard; MindRoom gives each one a Matrix account, and you talk to them in threads in MindRoom Chat — or any other Matrix client you already use.
Because Matrix bridges to other platforms, the same agents also work in Slack, Telegram, Discord, WhatsApp, IRC, and email — with the same persistent memory everywhere. Self-host the whole stack, or run only the MindRoom backend locally and pair it with hosted Matrix at mindroom.chat.
config.yaml; a built-in router picks the responder when you don't @-mention one, and mentioning several agents makes them collaborate in a thread.todo planner, with sandboxed execution and per-tool approval rules.!schedule), including silent checks that post only when they find something, plus supervised background Python watchers that can call governed agent tools and wake the agent only when something changes.!model and !room_model); route sensitive rooms to local Ollama and everything else to a cloud model.!reload-plugins.config.yaml and plugin changes apply live without bringing down the stack, and conversations resume seamlessly after a restart: session history and turn state are durable on disk, so agents pick up where they left off without double-replying.What it looks like:
You: @research @analyst @writer Create a competitive analysis report
Research: I'll gather data on our top 5 competitors...
Analyst: I'll identify strategic patterns and opportunities...
Writer: I'll compile everything into an executive summary...
Why we built this
Every AI app is a silo:
Your human team collaborates across Slack, Discord, Telegram, and email every day — your AI should too. MindRoom agents live in one place (Matrix) and follow you everywhere via bridges, with their memory intact.
Federation even lets agents cross organization boundaries:
Your client asks in their Discord:
Client: Can our architect AI review this with your team?
You: Sure! @assistant please collaborate with them
Your Assistant: [Joins from your Matrix server]
Client's Architect AI: [Joins from their server]
Together: [They review architecture, sharing context from both organizations]
Two AI agents from different companies collaborating — impossible with app-bound assistants.
PAID VERSION → FREE ALTERNATIVE
AI + CREATOR TOOLS
MARKETING + BUSINESS
DEVELOPER + TECH
DATA + ENGINEERING + PROFESSIONAL
MORE FREE ALTERNATIVES
300 PAID TOOLS.
300 FREE ALTERNATIVES.
@TheMeerkat multi domain support?
@LoudLemur It's the same.
@firmansi like nocodb, it's a separate url, as another n8n instance would be as well.
@firmansi can you work around as a second n8n instance or another webhook provider?
As of June 2026 (only 22 years late), HTTP has a new method - a GET with a body
Meet QUERY (RFC 10008).
It lets you send complex queries in the body (like POST) while staying safe, idempotent, and cacheable (like GET). Already works on servers (Node.js, Go, Laravel…).
Browsers are still adding full support, usable now with care, with widespread adoption coming later in 2026+.
May be the beginning of the end of ?query¶ms

Right, and to learn more why this is unfeasible look at how DNS MX records work.
They don't have a way to specify a port other than the defaults we all use.
SnappyMail is not a mail server.
So to replace it, you only need an alternative front end mail app that will use the built-in Cloudron (Haraka) mailserver.
@LoudLemur https://forum.cloudron.io/post/127984
GH says it can be a direct upgrade for existing SnappyMail installs.
Not sure that applies for custom packages, but if the CL team decide to include a migration script, it would work.
@luckow That's a lot of jokes.
I assume Thunderbird has this working.
The base image was recently updated too
There is a critical vulnerability being actively exploited on BTC Pay Server, which can result in the loss of funds.
Please update your BTC Pay Server to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTC Pay Server to prevent unauthorized access until you can update.
@ChristopherMag You're welcome.
I invite all of us to listen to our intuition more carefully.