@sparkwise

This is nice but not strictly necessary.

It is very nice indeed but being necessary or not is relative to how much features one wants to make life easier and getting nearer to what's offered by Big techs and SaaS in the like.

So, if that specific function can be fixed for that app I'd say it should be. Of course nothing is absolute lol 😆

@imc67 are you referring to the chatwoot nokogiri security issue bullet point? The upstream project has provided no information on how severe it is. I couldn't find nokogiri in the diffs either, would appreciate any info on this. They have no info on their blog either.

As for AdGuard, it has already been updated to support ipv6 (which is not backward compatible tested with 7.0). Also, the security issues from what I see are Go related things which are kinda unlikely because AdGuard is not exposed to the world.

In contrast, for clear security posts like https://about.gitlab.com/releases/2022/02/25/critical-security-release-gitlab-14-8-2-released/ , we make it available asap for 7.0.

The latest package fixes this. Docs are at https://docs.cloudron.io/apps/chatwoot/#rails-console

@apoim You can place custom environment variables in /app/data/env file https://docs.cloudron.io/apps/chatwoot/#custom-config . Essentially you set the config variables that are listed in https://www.chatwoot.com/docs/self-hosted/configuration/features/integrations/facebook-channel-setup#configuring-the-environment-variables-in-chatwoot in that file.

@imc67 Awesome and happy to hear that.

PS: I know that feeling - a fellow FF user.

@girish in my understanding, yes. Taken from here https://www.chatwoot.com/docs/self-hosted/telemetry

@imc67 I have not found anything about LDAP in the documentation. https://www.chatwoot.com/docs/self-hosted
There is a GitHub issue about "Oauth integration". https://github.com/chatwoot/chatwoot/issues/1318 Let's see.

@ianhyzy this sounds more like an upstream app bug. Do you see any errors in the app or browser logs which might lead to this?