@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.

@iamthefij said in .io, or not .io, is that even a question ?: Still, branding is powerful and rebranding something is a huge risk. I wouldn't recommend Cloudron attempt it. But the .io domain is not part of the Cloudron brand imho (it's not like it's in the logo or anything). TBH I think if all existing Cloudron.io domains just seamlessly 301 redirected to another TLD I doubt many people would even notice. I don't personally think it's a huge deal. But some people are quite passionate about it and do think it is a big deal, associated as it is with colonialism. Personally if I were the owner of a business with a .io domain I think I probably would change it, much like draw.io did (despite the fact they DO have it as part of the their brand).

@svtx life of a teenager

@joseph we dont have one. our needs are very specific. we have members who are encouraged to produce for us and they receive rewards in the form of room booking and payments in tokens....

@andreasdueren yeah. I meant the server, but it sounds like you found the reason!

@joseph Many thanks for the clear and detailed explanation!