@imc67 CIFS has to be tested on your specific mount because each CIFS mount is totally different (since it's network based and also depends on remote disk speed etc). But it's good to have a ball park number in any case.
Agree would be good to add, currently you can already just setup the DNS records with AAAA to point to the Cloudron and that should work fine. I think the automation of that is just what is lacking, next to maybe some mail DNS record related things, but not 100% sure.
Given that ipv4 is supported everywhere and at least I am not aware of a VPS provider who does not give ipv4 addresses, we have handled that as low priority so far.
I am curious in which circumstances you have ipv6 only clients? Maybe we are missing a crucial use-case.
@necrevistonnezr True, but imapfilter ( or another workaround ) is here today for you to achieve what you want. Beats waiting for the feature you're asking for which might be available sometime soon, later .... or never.
@girish No, I don't have a lot of experience with postgresql. The strategy you describe aligns with my understanding of mysql's philosophy, but postgresql seems to require admins be more explicit. E.g. granting permissions to an arbitrary quoted LIKE pattern is documented in mysql, but postgresql's GRANT docs don't mention anything of the like and look like they require the specific object to exist (by nature of being a valid identifier) before granting permissions. Though I could be mistaken.
@marcusquinn the API is also BitPay compatible btw. I think Coinbase is okay. In an ideal world, a public ledger really is the best. Since you and I both know that's not the world we live in, Monero serves an understandable need currently unsolved by Bitcoin. But that's the beauty of open source, right?
Thankfully, I have heard it is not hard to get a Monero daemon and payment integration running on btcpayserver via a docker flag. Along with an officially supported WordPress plugin, Point-of-Sale, crowdsourcing, shop, and invoice functions for any supported currency, this makes a nice little package for someone to get their community started with cryptocurrency.
Honestly, given that so many money services support purchasing BTC these days with QR-code scanning/sending and whatnot, I think giving Cloudron users the ability to get this going would be great. It may resonate with the kind of people looking for a self-hosted setup.
@jdaviescoates Agreed. Likely not an issue for a server with only a few apps, but can be a quick time saver for that at-a-glance info when hosting many of them. I'd personally like to see a toggle that allows this for admins so that it's not there for people who don't want to see them. But that can always be second iteration. haha.
That's great work @girish - it's not often you step out for the day and return to see your post "solved". I was going to include that it should be a simple nginx config thing but I know better. And it's unfortunate the request caching is a nightmare to enforce "must-staple".
Regardless, the win here is that you have it enabled. That should now be reflected in test reults from Mozilla Observatory (extended to Qualys SSL Labs & ImmuniWeb). Thanks for putting in the grunts on this one.
I don't have a script but if you want to keep the downtime low, we added this dry run feature last release - https://docs.cloudron.io/backups/#dry-run . This way you don't need to shutdown the old server while things are restoring on the new server. Of course, you have to be careful not to add new data in the old server since it won't be part of the backup but atleast the site will be up.
Right, we are actually fixing notification for the next release (6.3). In the meantime, Domains -> Renew all certs and then check the logs (button on the same page) if it fails. Usually, Let's Encrypt errors are temporary and currently Cloudron is a bit overzealous reporting those errors.
For reference, Haraka has a greylisting function built in: http://haraka.github.io/plugins/greylist/ - and it works with the DNSWL / whitelist which we should enable too. That way if an IP is on the DNSWL, it automatically skips any greylisting attributes.
@girish I think the issue with MySQL Workbench is I can't use the latest version as they don't support macOS 10.14 past a certain version, and a colleague on a later macOS can get it working on a later MySQL Workbench version but I can't update my OS at the moment until some other software I use is updated to work with the later OS. Classic catch-22 on that one.
I think the solution to this should just be to use DBeaver, it's free on all platforms, and seems to work on all OS versions. too.
Maybe better to save your time for the odd additional /phpmyadmin/ that might be useful on certain apps.
Certainly appreciate the help and looking, but I don't want to distract you too much given it's a software version compatibility issue and not a Cloudron issue really. Thank you all the same though!!