Release 1.5.10

README-DEV.md

@@ -43,15 +43,15 @@ Matterbridge exports from:
 
 - NodeStorage classes.
 
-# ****\*\*****
+# \***\*\*\*\*\***
 
-A plugin must never install or import from `matter-node.js` or `matter.js` directly (neither as a dependency, devDependency, nor peerDependency), as this leads to a second instance of `matter.js`, causing instability and unpredictable errors such as "The only instance is Endpoint". 
+A plugin must never install or import from `matter-node.js` or `matter.js` directly (neither as a dependency, devDependency, nor peerDependency), as this leads to a second instance of `matter.js`, causing instability and unpredictable errors such as "The only instance is Endpoint".
 
 Additionally, when Matterbridge updates the `matter.js` version, it should be consistent across all plugins.
 
-# ****\*\*****
+# \***\*\*\*\*\***
 
-A plugin must never install Matterbridge (neither as a dependency, devDependency, nor peerDependency). 
+A plugin must never install Matterbridge (neither as a dependency, devDependency, nor peerDependency).
 
 Matterbridge must be linked to the plugin in development only.
 
@@ -63,7 +63,7 @@ Matterbridge must be linked to the plugin in development only.
 }
 ```
 
-# ****\*\*****
+# \***\*\*\*\*\***
 
 In the next releases I will remove the duplicated exports so please update your plugins.
 

README-PODMAN.md

@@ -41,6 +41,7 @@ sudo chown -R $USER:$USER ./Matterbridge ./.matterbridge
 ```
 
 You may need to adapt the script to your setup:
+
 - ./Matterbridge is the position outside of the container of your matterbridge plugin directory (inside your home directory).
 - ./.matterbridge is the position outside of the container of your matterbridge storage directory (inside your home directory).
 
@@ -56,6 +57,7 @@ podman run --name matterbridge \
 ```
 
 You may need to adapt the script to your setup:
+
 - ~/Matterbridge is the position outside of the container of your matterbridge plugin directory.
 - ~/.matterbridge is the position outside of the container of your matterbridge storage directory.
 

README-SERVICE.md

@@ -106,11 +106,13 @@ sudo journalctl -u matterbridge.service -f --output cat
 ### Delete the logs older then 3 days (all of them not only the ones of Matterbridge!)
 
 Check the space used
+
 ```
 sudo journalctl --disk-usage
 ```
 
 remove all log older then 3 days
+
 ```
 sudo journalctl --rotate
 sudo journalctl --vacuum-time=3d
@@ -119,10 +121,13 @@ sudo journalctl --vacuum-time=3d
 ## Prevent the journal logs to grow
 
 If you want to make the setting permanent to prevent the journal logs to grow too much, run
+
 ```
 sudo nano /etc/systemd/journald.conf
 ```
+
 add
+
 ```
 Compress=yes            # Compress logs
 MaxRetentionSec=3days   # Keep logs for a maximum of 3 days.
@@ -131,7 +136,9 @@ ForwardToSyslog=no      # Disable forwarding to syslog to prevent duplicate logg
 SystemMaxUse=100M       # Limit persistent logs in /var/log/journal to 100 MB.
 RuntimeMaxUse=100M      # Limit runtime logs in /run/log/journal to 100 MB.
 ```
+
 save it and run
+
 ```
 sudo systemctl restart systemd-journald
 ```
@@ -152,7 +159,7 @@ If that is not the case, open the sudoers file for editing using visudo
 sudo visudo
 ```
 
-verify the presence of of a line 
+verify the presence of of a line
 
 ```
 @includedir /etc/sudoers.d
@@ -181,4 +188,3 @@ save the file and reload the settings with:
 ```
 sudo visudo -c
 ```
-

README.md

@@ -327,6 +327,7 @@ This will reset the internal storages. All commissioning informations will be lo
 ### Provide your own certificates
 
 Place your own certificates in the `.matterbridge/cert` directory:
+
 - `cert.pem`
 - `key.pem`
 - `ca.pem` (optional)
@@ -365,7 +366,6 @@ Then, from the dots menu in the frontend, download the `matterbridge.log` and `m
 
 ![image](https://github.com/user-attachments/assets/04ba65f6-594a-4ff8-9732-3df049f5a33e)
 
-
 # Known general issues
 
 ## Session XYZ does not exist

package.json

@@ -157,4 +157,4 @@
     "typescript": "5.6.2",
     "typescript-eslint": "8.8.0"
   }
-}
+}