@luckym said in Ability to go back within the installation setup wizard:

I wanted to restore Cloudron from a backup but in the setup wizard under "Domain Setup" mindlessly filled in the DNS information and clicked next instead of clicking on "Looking to restore".

I've done this before too.

Perhaps @staff could look at making the "Looking to restore" bit that's tiny at the bottom a lot more obvious?

And maybe even add another step afterwards that asks "are you actually looking to restore? go back" or something? 🤷

I attended one of DNSME's webinars, and they went over DNS failover. Most of it went over my head so fast I ended up with a buzzcut, but one thing was clear, DNSME is no ordinary DNS provider. They offer some really advanced features like failover, load balancing, traffic redirection, etc. and I really wish that's something I could make use of on Cloudron. It's definitely an overkill, but it's a move in the right direction.

@eddowding this is a feature request 🙂

I don't think you're the first to say it either. 🙂

Adding note to self: this app needs SYS_RAWIO capability.

@robi said in Add Cloudflare Storage as Backup target:

Is anyone using R2 with more than 10GB of data?

Does it flip into the paid tier if you have incrementally accumulated 11+GB in your current month? Or does it only count uploaded per month?

I've been pondering moving over, but would be interested to know this.

@jayonrails https://forum.cloudron.io/post/47122 🙂

yeah but it would be cool if it was deployed on the host server by default

i didn't know cloudron was like active directory. or had active directory builtin.

You can also use https://docs.cloudron.io/email/#subaddresses without having to add aliases at all.

This is pretty much covering my use case, great, thanks 👍

Ah, At-a-glance convenience image.png

... let's look closer at the new and improved Red notification....
WHAT!?
image.png

THIS IS A JOKE. ATTENTION> THIS IS A BAD ATTEMPT AT HUMOUR> I WILL DELETE THIS AFTER A FEW MINUTES>

Atleast, postgres does not have a way to limit db size - https://stackoverflow.com/questions/37822195/restrict-database-size

@nebulon thank you! I've managed to find a way around to keep automated updates keeping the risk of update failure to a minimum, but - don't you consider using btrfs or zfs's snapshots to work that around on the platform level?

Currently the quota import/export is not implemented, so I moved this over to the feature requests.

@girish there are no errors, just an empty reply.
though when i put "https" in front of it, it says certificate error, cant get local certificate issuer

@darsh_parsana it's not inside docker. Just ssh into the server and delete the files in /home/yellowtent/boxdata/mail/haraka-queue/. The command is also run in the server itself.

ooh yes, that works, my bad i was in the wrong folder

@nebulon just for information - livepatch doesn't mean you don't have to reboot - it just lets you postpone that moment as convenient.

For sync - a good practice on old good *nix is to issue sync twice before reboot - to make sure the buffers dumped for sure.

On the reboot automation using third-party apps - it's doable; everything is, but why, if you can just add it inside of the system?