@hakunamatata there is also Infomaniak, based in Switzerland, but atm it's not yet implemented in Cloudron, maybe one day (feature request here) ? So we need to manage DNS records manually.

@LoudLemur said in AI on Cloudron: MCP (Model Context Protocol) https://modelcontextprotocol.io/introduction According to the CEO of Anthropic, this is what is going to be writing 90% of code in 6 months, and almost all of it by the end of the year. MCP has been adopted by OpenAI and will hence be the de-facto standard https://techcrunch.com/2025/03/26/openai-adopts-rival-anthropics-standard-for-connecting-ai-models-to-data/ In a post on X on Wednesday, OpenAI CEO Sam Altman said that OpenAI will add support for Anthropic’s Model Context Protocol, or MCP, across its products, including the desktop app for ChatGPT. MCP is an open source standard that helps AI models produce better, more relevant responses to certain queries.

@girish said in Where does Cloudron fit best?: Is there a way to apply? Just go to the website and click the chat icon in the right corner

Yeah, it’s mind-boggling that this is still a problem unsolved. MusicBrainz is ok for some music styles but seriously shite for e.g. electronic music between 1990-2000, in particular for whitelabel releases… I use MP3Tag with various scripts and pull from the sources mentioned above as well as Beatport and Traxsource…

@robi yeah, might be interesting. Happy to test things out if someone can do a prototype package.

@Stefan Yes, everything works. Just install it on your Cloudron instance.

@BhargavRJ you need some couple of upvotes before people able to participate. You should have this now.

@BrutalBirdie Oh interesting, I didn't know that but yeah makes sense. Thx for the input !

@scooke Agreed, there is nothing attractive about their BYOVM offer.

I've added the json template in the tutorial in chapter 3 "3) n8n => THE FUN PART !"

@joseph said in Why does refreshing Disk Usage take so long?: but you can skip that backup disk from disk usage check . See the bottom of https://docs.cloudron.io/system/#disk-usage . Just add the path into /home/yellowtent/platformdata/diskusage/exclude I don't want to skip it! It was the one I wanted to check!

@jdaviescoates Good to know. Thank you!

@Kubernetes Thanks for sharing your experiences. I can see definite advantages of picking a cloud vendor and sticking with them for ease of migrating snapshots and VPS backups. We tend to do that, but then cloud vendors are always introducing surprises (price increases, bandwidth limits, etc) that make you question whether your current provider is worth keeping. So far I haven't found a way to take a snapshot from Vendor A and restore it to Vendor B, but perhaps it is available from a 3rd party.

@jdaviescoates said in How do you gather interest, collect and send email?: TBH, I'd probably just set-up a Ghost with a Mailgun newsletter. Right, that's the easy thing, but doesn't keep data local. Nice find on the n8n workflow, will take a look.

+1 It would be really great if we could have a second configuration field in the "Branding" tab that can explicitly set the value of the CLOUDRON_OIDC_PROVIDER_NAME with a fallback to the Cloudron name. Setting the same Cloudron name for all instances that connect to an LDAP just isn't a feasible solution in my opinion and makes administration chaotic. Non-Technical Users could also really benefit from a name like "Login with One-Click" - and naming the whole instance One-Click just feels like a bad idea.

@Neiluj I like the idea of the footer. In the past, we have always used different logos for different instances.

Can confirm we got the mail with empty subject too

@jdaviescoates We use a service called DNSMadeEasy. They've been acquired by DigiCert. They have a lot of nice features and reasonable prices that allow you grow in small increments. In our "package" a certain number of DNS queries are included. If we exceed the limit, we can buy more queries. Our practice was to use the lowest TTL possible, often using a value of 180. But as customer web traffic grew, we got closer to our limit. To prevent an overage, we increased TTL strategically which reduced queries. Hope this answers your questions.