[1.14.8]
Update AdGuardHome to 0.107.69
Full Changelog
DHCP settings could not be saved ([#8075]).
DNS Rewrite edit modal did not populate with the correct values ([#8072]).
The outdated querylog anonymization script.
There are plenty of use cases for Code-Server without DooD/DinD.
yes, currently used for multiple user instances on cloudron, mostly foam, some thunder, etc
As for the dev part, i solved it with hack mounting a custom external /nix into the required instances + https://devenv.sh/
nix is generally a cool architectural option for cloudron to look into imho and would love to help qualify such/the opportunity.
[1.82.0]
Update vault to 1.21.0
Full Changelog
auth/ldap: fix MFA/TOTP enforcement bypass when username_as_alias is enabled.
activity: Renamed timestamp in export API response to token_creation_time.
http: Add JSON configurable limits to HTTP handling for JSON payloads: max_json_depth, max_json_string_value_length, max_json_object_entry_count, max_json_array_element_count.
AES-CBC in Transit (Enterprise): Add support for encryption and decryption with AES-CBC in the Transit Secrets Engine.
KV v2 Version Attribution: Vault now includes attribution metadata for versioned KV secrets. This allows lookup of attribution information for each version of KV v2 secrets from CLI and API.
Login MFA TOTP Self-Enrollment (Enterprise): Simplify creation of login MFA TOTP credentials for users, allowing them to self-enroll MFA TOTP using a QR code (TOTP secret) generated during login. The new functionality is configurable on the TOTP login MFA method configuration screen and via the enable_self_enrollment parameter in the API.
activity (enterprise): Fix development_cluster setting being overwritten on performance secondaries upon cluster reload.
auth/cert: Recover from partially populated caches of trusted certificates if one or more certificates fails to load.
auth/spiffe: Address an issue updating a role with overlapping workload_id_pattern values it previously contained.
core: Role based quotas now work for cert auth
@necrevistonnezr no worries
Here's the latest:
The additional changes implemented yesterday allow existing users to keep their login password when changing the authentication provider from "default" or "local" to "oidc" (now also in combination with 2FA if enabled for the account).
Our documentation has been updated accordingly:
* https://docs.photoprism.app/getting-started/advanced/openid-connect/#existing-accounts
* https://docs.photoprism.app/known-issues/#openid-connect-oidc
Also note that admins cannot change the authentication provider of their own account through the Admin UI, so that they don't accidentally lock themselves out e.g. by setting it to "none".
Our own tests have been successful. However, we will give you some more time to test the preview build before tagging the new release. Many thanks to everyone who contributed, especially @moximoti who got things rolling and did much of the necessary work!
See https://github.com/photoprism/photoprism/issues/782#issuecomment-2222254616
I cannot believe I'd missed this thread! The last 2 years have been much hectic for me, and me who was finally about to start learning the process of building apps for Cloudron. I'm of course willing to participate and contribute in this in any way. @marcusquinn good suggestion.
[1.45.0]
Update chatwoot to 4.7.0
Full Changelog
SP Initiated SAML auth flow (Enterprise)
Support for custom tools in captain (Enterprise)
Health monitoring page for Whatsapp cloud channels
Email channel supports reply threads as quoted texts
UI to manage allowed domains for website widget
Support for lock to single thread in telegram channel
Support for incoming file attachments in line channel
Numerous bug fixes, UI fixes, and performance enhancements
@avatar1024 Right..
Impact is similar as with any shared VPS provider, and if you land on a busy host system, you can ask to be moved to one that is less. They now have implemented limits on resource sharing when a host system is at capacity not adding new VMs to it. The issue in the past was mostly I/O a bit on the low side, RAM & CPU being more than enough.
You'd want to make sure BBB can use more than 1 core effectively, so multithreading across without bottlenecks.
Network has also been fine in the NW US region, some hiccups in the S.
