@jdaviescoates

Hello @jamie_casper and welcome to the Cloudron Forum

@robi said: @LoudLemur would it be more discoverable if it was published as a blog or docs site and then include llms.txt and llms-full.txt to make parsing easier for the agents? Thanks, @robi You can see the blog here: https://wanderingmonster.dev/blog/cloudron-packaging-assessment-toolkit/

Thanks for sharing the solution!

Dedup FTW

@jdaviescoates said: I presume that if I have this setting enabled on multiple backup sites then whenever an app updates it'll first back-up to both locations? yes, it will back up to multiple locations and then update.

@robi great find! will give it a try.

I like the idea of using unbound and I've set it up. If I see something more interesting or accurate with the backups, I may come here with new insight. Thanks,

AI makes sense, will add.

@nebulon said in Czech Translation for Cloudron Now 100% Complete : This is great! We will ship the next Cloudron version then with Czech (internally 9.1 is released for new installs already, so will be added to the next patch release then) That’s great news, thank you!

@luckow thank you

That was just an intermediate release for pre-built images at cloud provider

You're going to be seeing alot more of these going forward. Https://Cognitum.one is another impressive FPGA+rPi4 for fast, ultra low power local AI agents

@girish said in Backups redundant?: @robi said in Backups redundant?: Made me ask to what would one restore this if not Cloudron (It's kind of special ! )? There is no standardized format for these backups, would have been great if there was one. One of my previous startups did have such a thing even though the focus was on app migration from any to any.

@charlesnw said in API docs bug: Are the docs generated from a git repo by chance? Yes, it's public at https://git.cloudron.io/docs/docs . Anyone can contribute!

Hello @3246 This can not be in the API since this is a file system setup.

So one approach I am using is to have 2 email servers on separate physical servers: current, archive. Archive becomes a mirror of current with respect to users. So user1@domain.com, user2@domain.com has user1@archivedomain.com, user2@archivedomain.com. If I am user1, I can have both accounts on all my devices (TBird, iOS, etc.). I then use this tool (https://imapsync.lamiral.info) to migrate current emails (but older) to archive. The tool is ugly, but works incredibly well. And since I only update the archive email server once or twice per year, I can backup less frequently since a backup from today has the same content as one generated 6 months ago. One of the other benefits is that I use SoGo EAS for current. The smaller the mailbox size the better it behaves. Security is not much stronger other than having a smaller blast radius and the need to penetrate 2 accounts instead of 1. If IMAP and POP3 could be disabled on the archive mail server and 2FA TOTP, passwordless, etc. be enabled to access webmail, that would be a better archive option.

With Mistral subscription I have almost infinite calls to Mistral API at not extra cost just by enabling the experiment mode in their subscription because no way I want to pay per token usage.

most likely 9.1 as we are done with 9.0 patch releases

Excellent, thanks @nebulon