Cloudron App Packagers
There are some 'breaking changes' on AgentZero from my last community app package. Their v1.15 uses a different architecture.
Deciding now on how to support 'migration' from old app to new app.
If anyone out there is using my CommunityApp, please do let me know.
It might influence how I handle migration ... or whether I even bother and just start fresh (yes, very lazy, but ultimately pragmatic).
girish said:
mail: admin notes field for mailboxes and lists
This is implemented. There is a notes field for each mailbox and list.
App is now signed.
Long-time bug-bear for me is switching between Spaces, Stage Manager, Mission Contol, blah blah blah, when you have multiple (like lots) of running apps. Especially when generally I hate depending on keyboard shortcuts (not enough viable w/o mental gymnastics).
So I made BarDock, my own minimal utility (well, why not?) :
Bit difficult to see here because it is intentionally tiny/unobtrusive (clearer on github repo).
https://github.com/slfhstr/BarDock
MIT licence - reciprocity to Cloudron and OSS communities who I have drawn so much support from.
I will get around to signing the app when I can stomach the process.
girish said:
Ubuntu 26.04 support
This is now implemented in master. Required very minimal changes, mostly to the installation script and also fixing up the docker version.
Ubuntu 26.04 is slowly appearing in many VPS providers (linode, vultr, upcloud) but not in DigitalOcean yet. So, haven't tested it extensively.
@marcusquinn sounds v good
Mac and Windows binaries now in releases if you want to try w/o cloning and building.
https://forgejo.tcjc.uk/cca/cloudron-portal-manager/releases
@micmc thank you
Windows build now fixed and shortly to be added to repo as installable file.
Easier for people to try out.
@girish no extra api needed.
In fact, possibly not enough used, and architecture needs review.
It's currently all browser tabs apart from the apps list, which is an api call.
I did it that way so apps could be launched in tabs inheriting the browser credentials.
But actually maybe I should have done it with more use of api calls.
Especially as I am struggling to build the Windows version with this approach (not a Windows user), so some review of approach may be needed.
Might have to treat this as PoC and implement in a slicker manner.
Selfishly my itch is scratched for Mac, as it's quite fast, and separated out from other browsing.
But I simply will not have Windows defeat me 
so I will look at re-working the approach.
Did you need any additional APIs ? Happy to add any if you need them.
