R
@p44 How I read it is that they designed it for CF, but each CF specific part has an alternative supported set of options, like DBs, from SQLite to Postgres, etc.
One implementation idea might be to also package a self-hosted container for Workers, so that all plugins you use across all EmDash sites might live there.
This is at least 2 different issues:
failures from Gmail to ocano domain (which should have bounces at Gmail)
self-hosted n8n to Gmail (which works reportedly) AND a local ocano mailbox (which doesn't)
It is very self hostable and has built in migration from WP sites among other goodies.
Definitely something to add to Cloudron.
@p44 You are very welcome.
Now making a tool to parse those IPs for the Cloudron block list is something an eager LLM agent could do.
@jdaviescoates All good, clearly it can't be more specific ;-]
Banhammer time
Assuming it is listening on port 4318, you can't do https with localhost.
Dropping the 's' should work if the API route is available.
@micmc it will work in LAMP if you set the HOME environment variable to /app/data, then npm will have a place to write to.
This would be great for the demo server to gain insights into how folks use the UI, session replay 
@luckow Great idea, many outdated things need a modern refresh, especially all the chat apps and protocols bridging to a PBX, kinda like what OpenClaw did.
Then there's the @mirotalk-57bab571 class apps that could benefit from such a gateway too.
There are many old large businesses that would go for this too.
Forge On!
One thing that may help a lot is @marcusquinn 's aidevops.sh project and the cloudron app he just made. Have many agents build out what you need when you need it.
Code abundance.
If it's pulling in lots of dependencies such as chrome which is a few gb it could blow through the timeout
