Cloudron Forum

@bmann said in Github Actions documentation/example for Surfer:

/website/*

This is a bit weird. In the output above it complains that it cannot find /website/, while in your yaml you are passing website/. The first one would be no surprise if it does not work, the second one however should work as ci tools usually open a shell where you will be directly in your git checkout.

I would try to debug this with inserting a few ls and pwd into your yaml to see where you actually are and if this might be a permission issue of some kind.

@rmdes said in Custom Cloudron image for ElasticSearch:

I'd certainly contribute with funding, even more if the app can then be used by other cloudron apps (if possible)

Nextcloud being such a candidate

@bmann said in Standard package formats:

Effectively: what is the difference between some-form-of-buildpacks and Cloudron's current packaging format?

Good question. You should find the information you need in https://docs.cloudron.io/packaging/manifest/

@LoudLemur _DNSLink is a feature of the IPFS protocol that you map a TXT record of the hash of the root of your published website or app and then CNAME at a single IPFS gateway. This means you don’t need to run a gateway for each domain.

Setting up the sieve rule means I have to have the password and set all of that up.

Using the "mailing list" settings means I don't have to do any of that, don't need to create an inbox, and it doesn't need to be owned by any accounts (and cloudron users with email admin / admin / superadmin can modify as needed).

Screen Shot 2023-12-15 at 5.08.26 PM.png

So I guess I answered my own question 🙂 I'll write it up. for people who ask in the future. "How do I set up email forwarding to external accounts without having to provision Cloudron accounts" == mailing list.

@luckow thanks for the SoGo -- looks like that does take care of everything.

Yeah, the access key is what is going to check if the domain is there. I think "Skip nameserver validation for custom Route53 NS names" would get me there 🙂

And all of the DNS and Email stuff...I totally understand how difficult it is to give less technical users the ability to even USE this stuff, as well as support slightly more advanced users. You're doing a great job!

@bmann This helped me after updating to 8.0 which broke IPv6 for some reason 🙂 (I'm also on OVHcloud)

It's the same with SOGo. Use the mailbox name as username and any of the group's credentials as the password.

Yes I have DKIM setup. Thanks for the “relaxed” incantation. I’ll try that.

Thanks @nebulon for the prompt fix!

@bmann said in WordPress Migrate Feedback, SMTP Mailer Instructions:

This is a restriction in the All-in-One WP plugin

Like @scooke says, if we're talking about the same plugin, it isn't. As I said, I recently did one over 1GB.