There appears to be an official chart for the entire Matrix stack. Given some of the complications with the existing chart, it may be worth migrating to this one. Retaining data will be challenging but informative.
There appears to be an official chart for the entire [Matrix stack](https://github.com/element-hq/ess-helm/tree/main/charts/matrix-stack). Given some of the complications with the existing chart, it may be worth migrating to this one. Retaining data will be challenging but informative.
eric
added this to the 2025:Q2 milestone 2025-05-12 01:51:54 +00:00
A useful link for configuring MAS with this new chart.
A useful [link](https://github.com/element-hq/ess-helm/blob/main/docs/advanced.md#configuring-matrix-authentication-service) for configuring MAS with this new chart.
Also, I have saved the existing signingKey from my current Matrix deploy to my Ansible vault. I believe this along with a preserved database will allow me to persist data across these installations.
Also, I have saved the existing `signingKey` from my current Matrix deploy to my Ansible vault. I believe this along with a preserved database will allow me to persist data across these installations.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
There appears to be an official chart for the entire Matrix stack. Given some of the complications with the existing chart, it may be worth migrating to this one. Retaining data will be challenging but informative.
A useful link for configuring MAS with this new chart.
Also, I have saved the existing
signingKeyfrom my current Matrix deploy to my Ansible vault. I believe this along with a preserved database will allow me to persist data across these installations.Duplicated in DevOps/ansible-role-matrix-stack#1.