jprusch

Hm, works here: Mattermost 7.1.0 with Collabora Plugin 1.1.0 We had an issue that the Collabora Online Address (URL) was somehow changed to the Mattermost server site URL. Not sure...

We use Nginx as proxy for Collabora: ``` server { listen 443 ssl; server_name collabora.OURDOMAIN; ssl_certificate /etc/ssl/OUR_BUNDLE.crt; ssl_certificate_key /etc/ssl/OUR_KEY.key; # static files location ^~ /browser { proxy_pass http://127.0.0.1:9980; proxy_set_header Host...

Well, I've no idea about "caddyserver". Can you access your CODE server with https://CODE-SERVER/hosting/discovery (assuming you use TLS/SSL). This should return an xml page, startung with: ``` ... ``` If...

We use a local CODE instance & not the docker image, so I'm not sure, if any settings in the CODE configuration inside the docker image must be changed. I...

Well that forces customers who have a strong MySQL knowledge to switch to PostgreSQL presumingly leading to more support requests. Performance might be an issue on high-scale implementations for thousands...

I'm also following the performance channel on Community https://community.mattermost.com/core/pl/jfbu7hyaffnffjicjo19tuxbfh It would be more honest to just say that two supported RDBMSs is one too much & there is no manpower...

Pretty sure we've to go thru: https://docs.mattermost.com/manage/bulk-export-tool.html

Many customers still use MySQL and as long as there is no clear & easy migration part, there will be no customer-based feedback on the AI plugin. I'm still willing...

I can only repeat: As long as there is not clear and easy migration process, you won't get any feedback of customers already on MySQL. Nobody sets up a new...

TBH, without a working migration from MySQL to Postgres, not only for this plugin, all customers/users still on MySQL cannot test anything on the various new features. A working migration...