#dsm7 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dsm7, aggregated by home.social.
-
Software testing is such an undervalued discipline. We all know how much software quality has declined in operating systems like #macOS and how Apple struggles to get things back on track.
Enter #Synology saying: hold my NAS, rendering LED Brightness setting dysfunctional with the #DSM7.3 update 🙄
At least they followed up with a KB and workaround: community.synology.com/enu/forum/1/post/194794
Also kudos to them for finally allowing #2FA setup without a phone. They did a proper implementation allowing #passkey creation and when doing that, removing the password. So great job in that department 👍 -
Software testing is such an undervalued discipline. We all know how much software quality has declined in operating systems like #macOS and how Apple struggles to get things back on track.
Enter #Synology saying: hold my NAS, rendering LED Brightness setting dysfunctional with the #DSM7.3 update 🙄
At least they followed up with a KB and workaround: community.synology.com/enu/forum/1/post/194794
Also kudos to them for finally allowing #2FA setup without a phone. They did a proper implementation allowing #passkey creation and when doing that, removing the password. So great job in that department 👍 -
Software testing is such an undervalued discipline. We all know how much software quality has declined in operating systems like #macOS and how Apple struggles to get things back on track.
Enter #Synology saying: hold my NAS, rendering LED Brightness setting dysfunctional with the #DSM7.3 update 🙄
At least they followed up with a KB and workaround: community.synology.com/enu/forum/1/post/194794
Also kudos to them for finally allowing #2FA setup without a phone. They did a proper implementation allowing #passkey creation and when doing that, removing the password. So great job in that department 👍 -
#Synology downgrade process is still valid for moving from #DSM7 7.2.2 back to 7.2.1 in case anyone wants back the option to use #VideoStation with no custom scripts.
Ofc, use this method only as a last resort!
https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/
You can always run #DSM inside a #virtual machine using #VMM, or even #Docker
https://www.blackvoid.club/how-to-run-synology-dsm-via-docker/
-
#Synology downgrade process is still valid for moving from #DSM7 7.2.2 back to 7.2.1 in case anyone wants back the option to use #VideoStation with no custom scripts.
Ofc, use this method only as a last resort!
https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/
You can always run #DSM inside a #virtual machine using #VMM, or even #Docker
https://www.blackvoid.club/how-to-run-synology-dsm-via-docker/
-
#Synology downgrade process is still valid for moving from #DSM7 7.2.2 back to 7.2.1 in case anyone wants back the option to use #VideoStation with no custom scripts.
Ofc, use this method only as a last resort!
https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/
You can always run #DSM inside a #virtual machine using #VMM, or even #Docker
https://www.blackvoid.club/how-to-run-synology-dsm-via-docker/
-
#Synology downgrade process is still valid for moving from #DSM7 7.2.2 back to 7.2.1 in case anyone wants back the option to use #VideoStation with no custom scripts.
Ofc, use this method only as a last resort!
https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/
You can always run #DSM inside a #virtual machine using #VMM, or even #Docker
https://www.blackvoid.club/how-to-run-synology-dsm-via-docker/
-
#Synology downgrade process is still valid for moving from #DSM7 7.2.2 back to 7.2.1 in case anyone wants back the option to use #VideoStation with no custom scripts.
Ofc, use this method only as a last resort!
https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/
You can always run #DSM inside a #virtual machine using #VMM, or even #Docker
https://www.blackvoid.club/how-to-run-synology-dsm-via-docker/
-
Also, the release notes state that:
- Surveillance Station on DSM will continue to support server-side processing of AVC (H.264) streams
- Deep Video Analytics (DVA) series models and VisualStation clients will retain support for AVC (H.264) and HEVC (H.265) codecs
So that means that H265 camera support will not work outside DVA devices. Including their own models (that support both codecs).
Sent a confirmation question on this one.
-
Also, the release notes state that:
- Surveillance Station on DSM will continue to support server-side processing of AVC (H.264) streams
- Deep Video Analytics (DVA) series models and VisualStation clients will retain support for AVC (H.264) and HEVC (H.265) codecs
So that means that H265 camera support will not work outside DVA devices. Including their own models (that support both codecs).
Sent a confirmation question on this one.
-
Also, the release notes state that:
- Surveillance Station on DSM will continue to support server-side processing of AVC (H.264) streams
- Deep Video Analytics (DVA) series models and VisualStation clients will retain support for AVC (H.264) and HEVC (H.265) codecs
So that means that H265 camera support will not work outside DVA devices. Including their own models (that support both codecs).
Sent a confirmation question on this one.
-
Also, the release notes state that:
- Surveillance Station on DSM will continue to support server-side processing of AVC (H.264) streams
- Deep Video Analytics (DVA) series models and VisualStation clients will retain support for AVC (H.264) and HEVC (H.265) codecs
So that means that H265 camera support will not work outside DVA devices. Including their own models (that support both codecs).
Sent a confirmation question on this one.
-
Also, the release notes state that:
- Surveillance Station on DSM will continue to support server-side processing of AVC (H.264) streams
- Deep Video Analytics (DVA) series models and VisualStation clients will retain support for AVC (H.264) and HEVC (H.265) codecs
So that means that H265 camera support will not work outside DVA devices. Including their own models (that support both codecs).
Sent a confirmation question on this one.
-
Well, it's close no doubt about that. The new #DSM7 (7.2.2) from #Synology will arrive next week!
While it's only X.X.2 version make no mistake about it, DO NOT rush with an update if you are using your #NAS in a kind of multimedia scenario. This version has some major changes, and one proof is #PLEX and its latest 1.41.xx update.
We can also see that the download list on their site specifically lists the 7.2.2 version along with the DSM 7.2.
-
Well, it's close no doubt about that. The new #DSM7 (7.2.2) from #Synology will arrive next week!
While it's only X.X.2 version make no mistake about it, DO NOT rush with an update if you are using your #NAS in a kind of multimedia scenario. This version has some major changes, and one proof is #PLEX and its latest 1.41.xx update.
We can also see that the download list on their site specifically lists the 7.2.2 version along with the DSM 7.2.
-
Well, it's close no doubt about that. The new #DSM7 (7.2.2) from #Synology will arrive next week!
While it's only X.X.2 version make no mistake about it, DO NOT rush with an update if you are using your #NAS in a kind of multimedia scenario. This version has some major changes, and one proof is #PLEX and its latest 1.41.xx update.
We can also see that the download list on their site specifically lists the 7.2.2 version along with the DSM 7.2.
-
Well, it's close no doubt about that. The new #DSM7 (7.2.2) from #Synology will arrive next week!
While it's only X.X.2 version make no mistake about it, DO NOT rush with an update if you are using your #NAS in a kind of multimedia scenario. This version has some major changes, and one proof is #PLEX and its latest 1.41.xx update.
We can also see that the download list on their site specifically lists the 7.2.2 version along with the DSM 7.2.
-
Well, it's close no doubt about that. The new #DSM7 (7.2.2) from #Synology will arrive next week!
While it's only X.X.2 version make no mistake about it, DO NOT rush with an update if you are using your #NAS in a kind of multimedia scenario. This version has some major changes, and one proof is #PLEX and its latest 1.41.xx update.
We can also see that the download list on their site specifically lists the 7.2.2 version along with the DSM 7.2.
-
Still running with #Synology #DSM6? Less then 1 year till end of life.
https://www.blackvoid.club/synology-dsm-6-2-end-of-life-announcement/
-
Still running with #Synology #DSM6? Less then 1 year till end of life.
https://www.blackvoid.club/synology-dsm-6-2-end-of-life-announcement/
-
Still running with #Synology #DSM6? Less then 1 year till end of life.
https://www.blackvoid.club/synology-dsm-6-2-end-of-life-announcement/
-
Still running with #Synology #DSM6? Less then 1 year till end of life.
https://www.blackvoid.club/synology-dsm-6-2-end-of-life-announcement/
-
Still running with #Synology #DSM6? Less then 1 year till end of life.
https://www.blackvoid.club/synology-dsm-6-2-end-of-life-announcement/
-
CW: Issues with Sonarr on Synology, boring tech post
Ugh. Right, after *another* folder annihiliation on the Synology server I have finally figured out which app was causing the issue - I'm posting it here on the random chance someone needs help with this and comes across it.
Server: #Synology #dsm7
Program: #Sonarr 3.0.10.1567 from the main update branch and built in mechanism - as vanilla as it could be.Evidently during an RSS synch Sonarr has failed to locate any searched items in the recordings list and has deleted my folder contents with the error "Recycling Bin has not been configured, deleting permanently". The recycling bin is available under advanced settings in media management and isn't turned on by default even if you are using the system's recycle bin - so there's no protection for this happening.
I don't know if it's linked but I had a list import error a few days ago related to #Plex authentication that shouldn't have anything to do with this but might - YMMV.
Anyway what is happening seems to be (since the last update) Sonarr has been querying the status of all 24 active shows in my list, finding no details of them somehow and deleting the folders in lieu of sending them to the recycle bin. They're not hidden, they're full on purged (already confirmed via CLI).
The reason I think it was linked to Plex is that it would happen after I had watched something on the LG OS Plex client - I suspect the act of using Plex triggered a watchlist push to the Plex server which then reported back to Sonarr. For some reason despite them not being at all related, Sonarr used that as an excuse to pull the RSS listing, find faults, and take action - there is no setting in Sonarr for deleting things in this way, it's doing it autonomously. Sonarr *can* delete empty folders if that option is enabled, but it wasn't.
Addendum: the logs indicate nothing being wrong before it starts this deletion process:
2023-08-12 07:07:54.9|Debug|Api|[GET] /api/v3/customFilter: 200.OK (13 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/languageprofile: 200.OK (1 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/qualityprofile: 200.OK (22 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/tag: 200.OK (28 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/series: 200.OK (86 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/importlist: 200.OK (52 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/config/ui: 200.OK (1 ms)
2023-08-12 07:07:55.4|Debug|Api|[GET] /api/v3/system/status: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/queue/status: 200.OK (2 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/config/indexer: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/indexer: 200.OK (10 ms)
2023-08-12 07:08:13.9|Debug|Api|[POST] /api/v3/indexer/action/newznabCategories: 200.OK (58 ms)
2023-08-12 07:08:19.6|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.6|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.6|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (11 ms)
2023-08-12 07:08:19.8|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.8|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.8|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (2 ms)
2023-08-12 07:08:19.9|Debug|RootFolderService|Generating list of unmapped folders
2023-08-12 07:08:19.9|Debug|RootFolderService|0 unmapped folders detected.
2023-08-12 07:08:19.9|Debug|Api|[GET] /api/v3/rootFolder: 200.OK (18 ms) -
CW: Issues with Sonarr on Synology, boring tech post
Ugh. Right, after *another* folder annihiliation on the Synology server I have finally figured out which app was causing the issue - I'm posting it here on the random chance someone needs help with this and comes across it.
Server: #Synology #dsm7
Program: #Sonarr 3.0.10.1567 from the main update branch and built in mechanism - as vanilla as it could be.Evidently during an RSS synch Sonarr has failed to locate any searched items in the recordings list and has deleted my folder contents with the error "Recycling Bin has not been configured, deleting permanently". The recycling bin is available under advanced settings in media management and isn't turned on by default even if you are using the system's recycle bin - so there's no protection for this happening.
I don't know if it's linked but I had a list import error a few days ago related to #Plex authentication that shouldn't have anything to do with this but might - YMMV.
Anyway what is happening seems to be (since the last update) Sonarr has been querying the status of all 24 active shows in my list, finding no details of them somehow and deleting the folders in lieu of sending them to the recycle bin. They're not hidden, they're full on purged (already confirmed via CLI).
The reason I think it was linked to Plex is that it would happen after I had watched something on the LG OS Plex client - I suspect the act of using Plex triggered a watchlist push to the Plex server which then reported back to Sonarr. For some reason despite them not being at all related, Sonarr used that as an excuse to pull the RSS listing, find faults, and take action - there is no setting in Sonarr for deleting things in this way, it's doing it autonomously. Sonarr *can* delete empty folders if that option is enabled, but it wasn't.
Addendum: the logs indicate nothing being wrong before it starts this deletion process:
2023-08-12 07:07:54.9|Debug|Api|[GET] /api/v3/customFilter: 200.OK (13 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/languageprofile: 200.OK (1 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/qualityprofile: 200.OK (22 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/tag: 200.OK (28 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/series: 200.OK (86 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/importlist: 200.OK (52 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/config/ui: 200.OK (1 ms)
2023-08-12 07:07:55.4|Debug|Api|[GET] /api/v3/system/status: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/queue/status: 200.OK (2 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/config/indexer: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/indexer: 200.OK (10 ms)
2023-08-12 07:08:13.9|Debug|Api|[POST] /api/v3/indexer/action/newznabCategories: 200.OK (58 ms)
2023-08-12 07:08:19.6|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.6|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.6|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (11 ms)
2023-08-12 07:08:19.8|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.8|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.8|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (2 ms)
2023-08-12 07:08:19.9|Debug|RootFolderService|Generating list of unmapped folders
2023-08-12 07:08:19.9|Debug|RootFolderService|0 unmapped folders detected.
2023-08-12 07:08:19.9|Debug|Api|[GET] /api/v3/rootFolder: 200.OK (18 ms) -
CW: Issues with Sonarr on Synology, boring tech post
Ugh. Right, after *another* folder annihiliation on the Synology server I have finally figured out which app was causing the issue - I'm posting it here on the random chance someone needs help with this and comes across it.
Server: #Synology #dsm7
Program: #Sonarr 3.0.10.1567 from the main update branch and built in mechanism - as vanilla as it could be.Evidently during an RSS synch Sonarr has failed to locate any searched items in the recordings list and has deleted my folder contents with the error "Recycling Bin has not been configured, deleting permanently". The recycling bin is available under advanced settings in media management and isn't turned on by default even if you are using the system's recycle bin - so there's no protection for this happening.
I don't know if it's linked but I had a list import error a few days ago related to #Plex authentication that shouldn't have anything to do with this but might - YMMV.
Anyway what is happening seems to be (since the last update) Sonarr has been querying the status of all 24 active shows in my list, finding no details of them somehow and deleting the folders in lieu of sending them to the recycle bin. They're not hidden, they're full on purged (already confirmed via CLI).
The reason I think it was linked to Plex is that it would happen after I had watched something on the LG OS Plex client - I suspect the act of using Plex triggered a watchlist push to the Plex server which then reported back to Sonarr. For some reason despite them not being at all related, Sonarr used that as an excuse to pull the RSS listing, find faults, and take action - there is no setting in Sonarr for deleting things in this way, it's doing it autonomously. Sonarr *can* delete empty folders if that option is enabled, but it wasn't.
Addendum: the logs indicate nothing being wrong before it starts this deletion process:
2023-08-12 07:07:54.9|Debug|Api|[GET] /api/v3/customFilter: 200.OK (13 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/languageprofile: 200.OK (1 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/qualityprofile: 200.OK (22 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/tag: 200.OK (28 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/series: 200.OK (86 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/importlist: 200.OK (52 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/config/ui: 200.OK (1 ms)
2023-08-12 07:07:55.4|Debug|Api|[GET] /api/v3/system/status: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/queue/status: 200.OK (2 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/config/indexer: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/indexer: 200.OK (10 ms)
2023-08-12 07:08:13.9|Debug|Api|[POST] /api/v3/indexer/action/newznabCategories: 200.OK (58 ms)
2023-08-12 07:08:19.6|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.6|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.6|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (11 ms)
2023-08-12 07:08:19.8|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.8|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.8|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (2 ms)
2023-08-12 07:08:19.9|Debug|RootFolderService|Generating list of unmapped folders
2023-08-12 07:08:19.9|Debug|RootFolderService|0 unmapped folders detected.
2023-08-12 07:08:19.9|Debug|Api|[GET] /api/v3/rootFolder: 200.OK (18 ms) -
CW: Issues with Sonarr on Synology, boring tech post
Ugh. Right, after *another* folder annihiliation on the Synology server I have finally figured out which app was causing the issue - I'm posting it here on the random chance someone needs help with this and comes across it.
Server: #Synology #dsm7
Program: #Sonarr 3.0.10.1567 from the main update branch and built in mechanism - as vanilla as it could be.Evidently during an RSS synch Sonarr has failed to locate any searched items in the recordings list and has deleted my folder contents with the error "Recycling Bin has not been configured, deleting permanently". The recycling bin is available under advanced settings in media management and isn't turned on by default even if you are using the system's recycle bin - so there's no protection for this happening.
I don't know if it's linked but I had a list import error a few days ago related to #Plex authentication that shouldn't have anything to do with this but might - YMMV.
Anyway what is happening seems to be (since the last update) Sonarr has been querying the status of all 24 active shows in my list, finding no details of them somehow and deleting the folders in lieu of sending them to the recycle bin. They're not hidden, they're full on purged (already confirmed via CLI).
The reason I think it was linked to Plex is that it would happen after I had watched something on the LG OS Plex client - I suspect the act of using Plex triggered a watchlist push to the Plex server which then reported back to Sonarr. For some reason despite them not being at all related, Sonarr used that as an excuse to pull the RSS listing, find faults, and take action - there is no setting in Sonarr for deleting things in this way, it's doing it autonomously. Sonarr *can* delete empty folders if that option is enabled, but it wasn't.
Addendum: the logs indicate nothing being wrong before it starts this deletion process:
2023-08-12 07:07:54.9|Debug|Api|[GET] /api/v3/customFilter: 200.OK (13 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/languageprofile: 200.OK (1 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/qualityprofile: 200.OK (22 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/tag: 200.OK (28 ms)
2023-08-12 07:07:55.0|Debug|Api|[GET] /api/v3/series: 200.OK (86 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/importlist: 200.OK (52 ms)
2023-08-12 07:07:55.3|Debug|Api|[GET] /api/v3/config/ui: 200.OK (1 ms)
2023-08-12 07:07:55.4|Debug|Api|[GET] /api/v3/system/status: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/health: 200.OK (0 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/queue/status: 200.OK (2 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/config/indexer: 200.OK (1 ms)
2023-08-12 07:07:56.0|Debug|Api|[GET] /api/v3/indexer: 200.OK (10 ms)
2023-08-12 07:08:13.9|Debug|Api|[POST] /api/v3/indexer/action/newznabCategories: 200.OK (58 ms)
2023-08-12 07:08:19.6|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.6|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.6|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (11 ms)
2023-08-12 07:08:19.8|Debug|SeriesService|Updating 0 series
2023-08-12 07:08:19.8|Debug|SeriesService|0 series updated
2023-08-12 07:08:19.8|Debug|Api|[PUT] /api/v3/series/editor: 202.Accepted (2 ms)
2023-08-12 07:08:19.9|Debug|RootFolderService|Generating list of unmapped folders
2023-08-12 07:08:19.9|Debug|RootFolderService|0 unmapped folders detected.
2023-08-12 07:08:19.9|Debug|Api|[GET] /api/v3/rootFolder: 200.OK (18 ms) -
In case you are still on #Synology #DSM6 with a #Plex setup on it, and you want to move to #DSM7 (7.2), go over this article for a smooth experience.
-
In case you are still on #Synology #DSM6 with a #Plex setup on it, and you want to move to #DSM7 (7.2), go over this article for a smooth experience.
-
In case you are still on #Synology #DSM6 with a #Plex setup on it, and you want to move to #DSM7 (7.2), go over this article for a smooth experience.
-
In case you are still on #Synology #DSM6 with a #Plex setup on it, and you want to move to #DSM7 (7.2), go over this article for a smooth experience.
-
In case you are still on #Synology #DSM6 with a #Plex setup on it, and you want to move to #DSM7 (7.2), go over this article for a smooth experience.
-
Updated the #Synology #DSM7 article on the topic of #push #notifications via #webhooks to reflect changes inside #DSM72,and along side #RocketChat, added the #Mattermost client as an example.
https://www.blackvoid.club/dsm-push-notifications-with-webhooks/
https://www.blackvoid.club/mattermost-free-open-source-messaging-platform/
-
Updated the #Synology #DSM7 article on the topic of #push #notifications via #webhooks to reflect changes inside #DSM72,and along side #RocketChat, added the #Mattermost client as an example.
https://www.blackvoid.club/dsm-push-notifications-with-webhooks/
https://www.blackvoid.club/mattermost-free-open-source-messaging-platform/
-
Updated the #Synology #DSM7 article on the topic of #push #notifications via #webhooks to reflect changes inside #DSM72,and along side #RocketChat, added the #Mattermost client as an example.
https://www.blackvoid.club/dsm-push-notifications-with-webhooks/
https://www.blackvoid.club/mattermost-free-open-source-messaging-platform/
-
Updated the #Synology #DSM7 article on the topic of #push #notifications via #webhooks to reflect changes inside #DSM72,and along side #RocketChat, added the #Mattermost client as an example.
https://www.blackvoid.club/dsm-push-notifications-with-webhooks/
https://www.blackvoid.club/mattermost-free-open-source-messaging-platform/
-
Updated the #Synology #DSM7 article on the topic of #push #notifications via #webhooks to reflect changes inside #DSM72,and along side #RocketChat, added the #Mattermost client as an example.
https://www.blackvoid.club/dsm-push-notifications-with-webhooks/
https://www.blackvoid.club/mattermost-free-open-source-messaging-platform/
-
How to Install Friendica on Your Synology NAS
https://mariushosting.com/how-to-install-friendica-on-your-synology-nas/
#Synology #NAS #Docker #Friendica #Social #SocialNetwork #Fediverse #Decentralized #selfhost #selfhosting #selfhosted #DSM #DSM7 #DSM72 -
How to Install Friendica on Your Synology NAS
https://mariushosting.com/how-to-install-friendica-on-your-synology-nas/
#Synology #NAS #Docker #Friendica #Social #SocialNetwork #Fediverse #Decentralized #selfhost #selfhosting #selfhosted #DSM #DSM7 #DSM72 -
How to Install Friendica on Your Synology NAS
https://mariushosting.com/how-to-install-friendica-on-your-synology-nas/
#Synology #NAS #Docker #Friendica #Social #SocialNetwork #Fediverse #Decentralized #selfhost #selfhosting #selfhosted #DSM #DSM7 #DSM72 -
How to Install Friendica on Your Synology NAS
https://mariushosting.com/how-to-install-friendica-on-your-synology-nas/
#Synology #NAS #Docker #Friendica #Social #SocialNetwork #Fediverse #Decentralized #selfhost #selfhosting #selfhosted #DSM #DSM7 #DSM72 -
How to Install Friendica on Your Synology NAS
https://mariushosting.com/how-to-install-friendica-on-your-synology-nas/
#Synology #NAS #Docker #Friendica #Social #SocialNetwork #Fediverse #Decentralized #selfhost #selfhosting #selfhosted #DSM #DSM7 #DSM72 -
Synology DSM 7.2 sucht erste Beta-Tester
Synology startet mit dem öffentlichen Beta-Test des DiskStation Manager 7.2. Interessierte Nutzer können die Vorabversion jetzt auf ihren NAS-Laufwerken installieren. Das nächste große Update für das Betriebssystem für die Netzwerkspeicher-Laufwerke von Synology hat unter anderem die Möglichkeit im Gepäck, Freigabeordner gegen die Änderung oder Löschung zu sperren und komplette Volumes zu verschlüsseln. Darüber hinaus wird […]
https://www.ifun.de/synology-dsm-7-2-sucht-erste-beta-tester-205641/
-
Synology DSM 7.2 sucht erste Beta-Tester
Synology startet mit dem öffentlichen Beta-Test des DiskStation Manager 7.2. Interessierte Nutzer können die Vorabversion jetzt auf ihren NAS-Laufwerken installieren. Das nächste große Update für das Betriebssystem für die Netzwerkspeicher-Laufwerke von Synology hat unter anderem die Möglichkeit im Gepäck, Freigabeordner gegen die Änderung oder Löschung zu sperren und komplette Volumes zu verschlüsseln. Darüber hinaus wird […]
https://www.ifun.de/synology-dsm-7-2-sucht-erste-beta-tester-205641/
-
Synology DSM 7.2 sucht erste Beta-Tester
Synology startet mit dem öffentlichen Beta-Test des DiskStation Manager 7.2. Interessierte Nutzer können die Vorabversion jetzt auf ihren NAS-Laufwerken installieren. Das nächste große Update für das Betriebssystem für die Netzwerkspeicher-Laufwerke von Synology hat unter anderem die Möglichkeit im Gepäck, Freigabeordner gegen die Änderung oder Löschung zu sperren und komplette Volumes zu verschlüsseln. Darüber hinaus wird […]
https://www.ifun.de/synology-dsm-7-2-sucht-erste-beta-tester-205641/
