@girish thank you.

I re-did all the steps manually as per your original message and got the same error.

The only major difference between your and my setup - it's token length - it's 257 characters long in my case.

Any clue?

@jlx89 said in App Pages:

This issue also affects admins like me who have to scroll through ~45 apps to find what I am looking for.

I tend to filter by group or domain first, or just use the search, to avoid excessive scrolling (but, yeah, before I got into that habit I scrolled lots)

@sam_uk I'm interested in this use case too. We want to incubate groups on our Cloudron until they've reached a size where they can afford their own.

@brutalbirdie thank you very much, appreciate that!
The need is not big enough, at least not for now, let me revert back to you, if it will appear to be so

@marcusquinn because it already exists 🙂

Best bet so far would be to do a Cloudron instance migration and set it up on a new subdomain. (Restore from backup in a new VPS)

@luckow Yes, similar view to the aliases ones where all are listed for the mailbox user.

I would love this for the app images. Ideally a build which was made today from a git tag and made 10 days ago from the same git tag should result in the same docker image. But currently, it doesn't. I don't know if this is a solved problem for docker. If there's any docs/ideas here, would be good to know.

DNSBLs are configurable in 6.4

@jdaviescoates I'm looking at a https://form.io/ > N8N > Cloudron API workflow. No idea if that's a good way though.

All the bits are FOSS, but form.io is not available on Cloudron yet.

@fbartels I do believe you.

There is a "Spam" filter type in next release - 6.4

@girish what about just a normal organization level rights separation?
I mean - it's really two different set of roles:

1st line support, dealing with mailboxes 2nd or 3rd, making sure the system and services are up and running.

I don't need hiding anything, I just want to ensure my users can manage they mailboxes and users for they own.

For now I have to temporary give admin permissions to the 1st line and that's kind of risky...

@girish WHOOP!!! Thank you!!

@fbartels Optimism and hope? /s

Great points.

@nebulon this is something for some "larger" sized organizations. As an example, a client that wants to switch to using cloudron - they have 50 or so users. It would be nice to automate the mailbox creation with initial sync and/or on-going (new users get a new mailbox and so on). Of course, this is mainly for external LDAP / AD.

@jdaviescoates we are discussing options there. It is a bit more complex given that the current pricepoint does not realistically justify hiring support resources for such app related tickets. Afterall we are neither the experts on bugs our users hit within the apps nor do we really want to head into a pure support based business, which obviously would be in our case time-intense and thus requiring an entirely different price tag. Of course a broken app instance has no use to anyone, which is why we are prioritizing such tickets currently.

Either way I am recovered now, so that is good 🙂

Good idea, I have been missing this myself. Quite trivial to add as well, just adding a db field and exposing it. We also have the equivalent keep field in the db schema already.

@murgero I didn't say it wouldn't be accessible; it would, just through my proxies, that make sure to remove any information, that would help in disclosure.

You also miss an option with Intranets.

@girish Awesome, thank you!

The latest lamp package support PHP 8.0

@fbartels This is a much better way to say it, yes.

Some way to communicate with my users in a semi-permanent way.

@marcusquinn Yeah, I for one would love for my screw-ups and poking-arounds to be recorded. Would sure save time on re-Googling commands!

It looks like my friends at Aporeto.com got acquired by PaloAlto Networks. They have an OSS projects called Trireme - https://github.com/aporeto-inc

Trireme, an open-source library curated by Aporeto to provide cryptographic isolation for cloud-native applications. Trireme-lib is a Zero-Trust networking library that makes it possible to setup security policies and segment applications by enforcing end-to-end authentication and authorization without the need for complex control planes or IP/port-centric ACLs and east-west firewalls.

Trireme-lib supports both containers and Linux processes as well user-based activation, and it allows security policy enforcement between any of these entities.

A good tool for Cloudron as well as securing LDAP across machines.

I'd still really like this small addition to the System Info page.

You shouldn't have to do sums in order to work out how much disk space is being used. It should just be displayed.

A simple feature to add with a decent benefit. +1!