New Crowdin updates (#34)

* New translations external-api.md (French)

* New translations _category_.json (French)

* New translations external-api.md (French)

* New translations docker.md (Romanian)

* New translations docker.md (French)

* New translations docker.md (Spanish)

* New translations docker.md (Afrikaans)

* New translations docker.md (Arabic)

* New translations docker.md (Bulgarian)

* New translations docker.md (Catalan)

* New translations docker.md (Czech)

* New translations docker.md (Danish)

* New translations docker.md (German)

* New translations docker.md (Greek)

* New translations docker.md (Finnish)

* New translations docker.md (Hebrew)

* New translations docker.md (Hungarian)

* New translations docker.md (Italian)

* New translations docker.md (Japanese)

* New translations docker.md (Korean)

* New translations docker.md (Dutch)

* New translations docker.md (Norwegian)

* New translations docker.md (Polish)

* New translations docker.md (Portuguese)

* New translations docker.md (Russian)

* New translations docker.md (Slovak)

* New translations docker.md (Slovenian)

* New translations docker.md (Serbian (Cyrillic))

* New translations docker.md (Swedish)

* New translations docker.md (Turkish)

* New translations docker.md (Ukrainian)

* New translations docker.md (Chinese Simplified)

* New translations docker.md (Chinese Traditional)

* New translations docker.md (Vietnamese)

* New translations docker.md (Icelandic)

* New translations docker.md (Portuguese, Brazilian)

* New translations docker.md (Persian)

* New translations docker.md (Bengali)

* New translations docker.md (Thai)

* New translations docker.md (Croatian)

* New translations docker.md (Estonian)

* New translations docker.md (English, United Kingdom)

i18n/af-ZA/docusaurus-plugin-content-docs/current/installation/docker.md

@@ -1,21 +1,28 @@
 # Docker
 
-Some of these steps may not apply to your installation.  Understand what they do, and ignore or customize as necessary.
+Some of these steps may not apply to your installation.  Understand what they do, and ignore, or customize as necessary.
 
-## Fedora Linux Preparation
+## Preparation
 
 For operating system support and service packages.
 
+### Debian Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/debian/
+
+### Fedora Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/fedora/
+
+#### Extra instructions
+
 ```
-sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo;
-sudo dnf install docker-ce;
 sudo usermod -a -G docker <username>;
 ```
 
 Re-login or restart the machine.
 
 ```
-sudo systemctl start docker;
 sudo mkdir /srv/UMS;
 sudo chcon -t svirt_sandbox_file_t /srv/UMS;
 sudo chown core:docker /srv/UMS;
@@ -26,14 +33,15 @@ Mount storage to host and link into that directory, probably read-only.
 
 ## Container Setup
 
-Mount following volumes and ports:
-- Media folder VOLUME /media
-- Profile folder containing UMS.conf VOLUME /profile
+Mount the following volumes:
+- Media folder `/media`
+- Profile folder containing UMS.conf `/profile`
 
 Expose/forward these ports from the host: 1044, 5001, 9001.
 
-The following scripts does those steps:
+The following scripts accomplish that (using the fish shell):
 ```
+sudo su -;
 set rootDir "/home/UMS/.config/UMS";
 mkdir -p "$rootDir/data";
 ​
@@ -77,9 +85,9 @@ docker cp <containerName>:/var/log/UMS/root/debug.log ./;
 
 Using Fedora CoreOS, I had access/permission denied problems trying to use bind mounts.
 
-It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional :Z as a suffix to the bind mount's descriptor option value allowed container write access to host files. :z can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
+It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional `:Z` as a suffix to the bind mount's descriptor option value allowed container write access to host files. `:z` can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
 
-Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run chcon -Rt svirt_sandbox_file_t host_dir, but that also seems discouraged.
+Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run `chcon -Rt svirt_sandbox_file_t` host_dir, but that also seems discouraged.
 
 Strangely this is not an issue on Fedora Workstation, but I guess installing it manually added a package to deal with this. Seems to be container-selinux.
 
@@ -101,4 +109,4 @@ Strangely this is not an issue on Fedora Workstation, but I guess installing it
 - https://github.com/UniversalMediaServer/UniversalMediaServer/blob/master/docker/Dockerfile
 - https://github.com/UniversalMediaServer/UniversalMediaServer/tree/master/src/main/external-resources
 - https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label
-- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view
+- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view

i18n/ar-SA/docusaurus-plugin-content-docs/current/installation/docker.md

@@ -1,21 +1,28 @@
 # Docker
 
-Some of these steps may not apply to your installation.  Understand what they do, and ignore or customize as necessary.
+Some of these steps may not apply to your installation.  Understand what they do, and ignore, or customize as necessary.
 
-## Fedora Linux Preparation
+## Preparation
 
 For operating system support and service packages.
 
+### Debian Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/debian/
+
+### Fedora Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/fedora/
+
+#### Extra instructions
+
 ```
-sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo;
-sudo dnf install docker-ce;
 sudo usermod -a -G docker <username>;
 ```
 
 Re-login or restart the machine.
 
 ```
-sudo systemctl start docker;
 sudo mkdir /srv/UMS;
 sudo chcon -t svirt_sandbox_file_t /srv/UMS;
 sudo chown core:docker /srv/UMS;
@@ -26,14 +33,15 @@ Mount storage to host and link into that directory, probably read-only.
 
 ## Container Setup
 
-Mount following volumes and ports:
-- Media folder VOLUME /media
-- Profile folder containing UMS.conf VOLUME /profile
+Mount the following volumes:
+- Media folder `/media`
+- Profile folder containing UMS.conf `/profile`
 
 Expose/forward these ports from the host: 1044, 5001, 9001.
 
-The following scripts does those steps:
+The following scripts accomplish that (using the fish shell):
 ```
+sudo su -;
 set rootDir "/home/UMS/.config/UMS";
 mkdir -p "$rootDir/data";
 ​
@@ -77,9 +85,9 @@ docker cp <containerName>:/var/log/UMS/root/debug.log ./;
 
 Using Fedora CoreOS, I had access/permission denied problems trying to use bind mounts.
 
-It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional :Z as a suffix to the bind mount's descriptor option value allowed container write access to host files. :z can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
+It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional `:Z` as a suffix to the bind mount's descriptor option value allowed container write access to host files. `:z` can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
 
-Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run chcon -Rt svirt_sandbox_file_t host_dir, but that also seems discouraged.
+Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run `chcon -Rt svirt_sandbox_file_t` host_dir, but that also seems discouraged.
 
 Strangely this is not an issue on Fedora Workstation, but I guess installing it manually added a package to deal with this. Seems to be container-selinux.
 
@@ -101,4 +109,4 @@ Strangely this is not an issue on Fedora Workstation, but I guess installing it
 - https://github.com/UniversalMediaServer/UniversalMediaServer/blob/master/docker/Dockerfile
 - https://github.com/UniversalMediaServer/UniversalMediaServer/tree/master/src/main/external-resources
 - https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label
-- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view
+- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view

i18n/bg-BG/docusaurus-plugin-content-docs/current/installation/docker.md

@@ -1,21 +1,28 @@
 # Docker
 
-Some of these steps may not apply to your installation.  Understand what they do, and ignore or customize as necessary.
+Some of these steps may not apply to your installation.  Understand what they do, and ignore, or customize as necessary.
 
-## Fedora Linux Preparation
+## Preparation
 
 For operating system support and service packages.
 
+### Debian Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/debian/
+
+### Fedora Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/fedora/
+
+#### Extra instructions
+
 ```
-sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo;
-sudo dnf install docker-ce;
 sudo usermod -a -G docker <username>;
 ```
 
 Re-login or restart the machine.
 
 ```
-sudo systemctl start docker;
 sudo mkdir /srv/UMS;
 sudo chcon -t svirt_sandbox_file_t /srv/UMS;
 sudo chown core:docker /srv/UMS;
@@ -26,14 +33,15 @@ Mount storage to host and link into that directory, probably read-only.
 
 ## Container Setup
 
-Mount following volumes and ports:
-- Media folder VOLUME /media
-- Profile folder containing UMS.conf VOLUME /profile
+Mount the following volumes:
+- Media folder `/media`
+- Profile folder containing UMS.conf `/profile`
 
 Expose/forward these ports from the host: 1044, 5001, 9001.
 
-The following scripts does those steps:
+The following scripts accomplish that (using the fish shell):
 ```
+sudo su -;
 set rootDir "/home/UMS/.config/UMS";
 mkdir -p "$rootDir/data";
 ​
@@ -77,9 +85,9 @@ docker cp <containerName>:/var/log/UMS/root/debug.log ./;
 
 Using Fedora CoreOS, I had access/permission denied problems trying to use bind mounts.
 
-It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional :Z as a suffix to the bind mount's descriptor option value allowed container write access to host files. :z can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
+It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional `:Z` as a suffix to the bind mount's descriptor option value allowed container write access to host files. `:z` can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
 
-Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run chcon -Rt svirt_sandbox_file_t host_dir, but that also seems discouraged.
+Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run `chcon -Rt svirt_sandbox_file_t` host_dir, but that also seems discouraged.
 
 Strangely this is not an issue on Fedora Workstation, but I guess installing it manually added a package to deal with this. Seems to be container-selinux.
 
@@ -101,4 +109,4 @@ Strangely this is not an issue on Fedora Workstation, but I guess installing it
 - https://github.com/UniversalMediaServer/UniversalMediaServer/blob/master/docker/Dockerfile
 - https://github.com/UniversalMediaServer/UniversalMediaServer/tree/master/src/main/external-resources
 - https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label
-- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view
+- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view

i18n/bn-BD/docusaurus-plugin-content-docs/current/installation/docker.md

@@ -1,21 +1,28 @@
 # Docker
 
-Some of these steps may not apply to your installation.  Understand what they do, and ignore or customize as necessary.
+Some of these steps may not apply to your installation.  Understand what they do, and ignore, or customize as necessary.
 
-## Fedora Linux Preparation
+## Preparation
 
 For operating system support and service packages.
 
+### Debian Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/debian/
+
+### Fedora Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/fedora/
+
+#### Extra instructions
+
 ```
-sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo;
-sudo dnf install docker-ce;
 sudo usermod -a -G docker <username>;
 ```
 
 Re-login or restart the machine.
 
 ```
-sudo systemctl start docker;
 sudo mkdir /srv/UMS;
 sudo chcon -t svirt_sandbox_file_t /srv/UMS;
 sudo chown core:docker /srv/UMS;
@@ -26,14 +33,15 @@ Mount storage to host and link into that directory, probably read-only.
 
 ## Container Setup
 
-Mount following volumes and ports:
-- Media folder VOLUME /media
-- Profile folder containing UMS.conf VOLUME /profile
+Mount the following volumes:
+- Media folder `/media`
+- Profile folder containing UMS.conf `/profile`
 
 Expose/forward these ports from the host: 1044, 5001, 9001.
 
-The following scripts does those steps:
+The following scripts accomplish that (using the fish shell):
 ```
+sudo su -;
 set rootDir "/home/UMS/.config/UMS";
 mkdir -p "$rootDir/data";
 ​
@@ -77,9 +85,9 @@ docker cp <containerName>:/var/log/UMS/root/debug.log ./;
 
 Using Fedora CoreOS, I had access/permission denied problems trying to use bind mounts.
 
-It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional :Z as a suffix to the bind mount's descriptor option value allowed container write access to host files. :z can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
+It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional `:Z` as a suffix to the bind mount's descriptor option value allowed container write access to host files. `:z` can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
 
-Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run chcon -Rt svirt_sandbox_file_t host_dir, but that also seems discouraged.
+Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run `chcon -Rt svirt_sandbox_file_t` host_dir, but that also seems discouraged.
 
 Strangely this is not an issue on Fedora Workstation, but I guess installing it manually added a package to deal with this. Seems to be container-selinux.
 
@@ -101,4 +109,4 @@ Strangely this is not an issue on Fedora Workstation, but I guess installing it
 - https://github.com/UniversalMediaServer/UniversalMediaServer/blob/master/docker/Dockerfile
 - https://github.com/UniversalMediaServer/UniversalMediaServer/tree/master/src/main/external-resources
 - https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label
-- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view
+- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view

i18n/ca-ES/docusaurus-plugin-content-docs/current/installation/docker.md

@@ -1,21 +1,28 @@
 # Docker
 
-Some of these steps may not apply to your installation.  Understand what they do, and ignore or customize as necessary.
+Some of these steps may not apply to your installation.  Understand what they do, and ignore, or customize as necessary.
 
-## Fedora Linux Preparation
+## Preparation
 
 For operating system support and service packages.
 
+### Debian Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/debian/
+
+### Fedora Linux
+
+Install Docker (Engine): https://docs.docker.com/engine/install/fedora/
+
+#### Extra instructions
+
 ```
-sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo;
-sudo dnf install docker-ce;
 sudo usermod -a -G docker <username>;
 ```
 
 Re-login or restart the machine.
 
 ```
-sudo systemctl start docker;
 sudo mkdir /srv/UMS;
 sudo chcon -t svirt_sandbox_file_t /srv/UMS;
 sudo chown core:docker /srv/UMS;
@@ -26,14 +33,15 @@ Mount storage to host and link into that directory, probably read-only.
 
 ## Container Setup
 
-Mount following volumes and ports:
-- Media folder VOLUME /media
-- Profile folder containing UMS.conf VOLUME /profile
+Mount the following volumes:
+- Media folder `/media`
+- Profile folder containing UMS.conf `/profile`
 
 Expose/forward these ports from the host: 1044, 5001, 9001.
 
-The following scripts does those steps:
+The following scripts accomplish that (using the fish shell):
 ```
+sudo su -;
 set rootDir "/home/UMS/.config/UMS";
 mkdir -p "$rootDir/data";
 ​
@@ -77,9 +85,9 @@ docker cp <containerName>:/var/log/UMS/root/debug.log ./;
 
 Using Fedora CoreOS, I had access/permission denied problems trying to use bind mounts.
 
-It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional :Z as a suffix to the bind mount's descriptor option value allowed container write access to host files. :z can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
+It may be recommended to use the Docker-managed, named-volumes capability instead, but to avoid that complexity, I found that the additional `:Z` as a suffix to the bind mount's descriptor option value allowed container write access to host files. `:z` can also be used instead, but security advice may suggest keeping resources more isolated between application/service environments, rather than shared.
 
-Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run chcon -Rt svirt_sandbox_file_t host_dir, but that also seems discouraged.
+Matching error messages can be seen using journalctl, so it is an SELinux problem. The solution for that would be to run `chcon -Rt svirt_sandbox_file_t` host_dir, but that also seems discouraged.
 
 Strangely this is not an issue on Fedora Workstation, but I guess installing it manually added a package to deal with this. Seems to be container-selinux.
 
@@ -101,4 +109,4 @@ Strangely this is not an issue on Fedora Workstation, but I guess installing it
 - https://github.com/UniversalMediaServer/UniversalMediaServer/blob/master/docker/Dockerfile
 - https://github.com/UniversalMediaServer/UniversalMediaServer/tree/master/src/main/external-resources
 - https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label
-- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view
+- https://drive.google.com/file/d/1ORNc113a8is1K1ZZtp1r3iz44uzJDeRp/view