Add plyr as player default and remove NodeJS, npm and videojs

docs/source/siteadmin/deploying.rst

@@ -42,10 +42,10 @@ alternative deployment options.
     Throughout the documentation we use the ``sudo`` command to indicate that
     an instruction requires elevated user privileges to run. You can issue
     these commands as the ``root`` user if you prefer.
-    
+
     If you need help configuring ``sudo``, see the
     `Debian wiki <https://wiki.debian.org/sudo/>`_ or the
-    `Fedora Project wiki <https://fedoraproject.org/wiki/Configuring_Sudo/>`_. 
+    `Fedora Project wiki <https://fedoraproject.org/wiki/Configuring_Sudo/>`_.
 
 
 Prepare System
@@ -63,7 +63,6 @@ MediaGoblin has the following core dependencies:
 - `Python Imaging Library <http://www.pythonware.com/products/pil/>`_
   (PIL or Pillow)
 - `virtualenv <http://www.virtualenv.org/>`_
-- `Node.js <https://nodejs.org>`_
 
 These instructions have been tested on Debian 11 and Fedora 33. These
 instructions should approximately translate to recent Debian
@@ -76,11 +75,11 @@ Issue the following commands:
 
     # Debian 11
     sudo apt update
-    sudo apt install automake git nodejs npm python3-dev \
+    sudo apt install automake git python3-dev \
     python3-gst-1.0 python3-lxml python3-pil virtualenv
 
     # Fedora 33
-    sudo dnf install automake gcc git-core make nodejs npm \
+    sudo dnf install automake gcc git-core make \
     libffi-devel python3-devel python3-lxml python3-pillow \
     virtualenv
 
@@ -169,7 +168,7 @@ MediaGoblin does not require special permissions or elevated
 access to run. As such, the preferred way to run MediaGoblin is to
 create a dedicated, unprivileged system user for the sole purpose of running
 MediaGoblin. Running MediaGoblin processes under an unprivileged system user
-helps to keep it more secure. 
+helps to keep it more secure.
 
 The following command will create a system account with a username of
 ``mediagoblin``.
@@ -191,10 +190,10 @@ read the media files that users upload (images, videos, etc.)
 Many operating systems will automatically create a group
 ``mediagoblin`` to go with the new user ``mediagoblin``, but just to
 be sure::
-  
+
     sudo groupadd --force mediagoblin
     sudo usermod --append --groups mediagoblin mediagoblin
-       
+
 No password will be assigned to this account, and you will not be able
 to log in as this user. To switch to this account, enter::
 
@@ -209,7 +208,7 @@ Create a MediaGoblin Directory
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You should create a working directory for MediaGoblin. This document
-assumes your local git repository will be located at 
+assumes your local git repository will be located at
 ``/srv/mediagoblin.example.org/mediagoblin/``.
 Substitute your preferred local deployment path as needed.
 
@@ -489,7 +488,7 @@ created::
     sudo find /opt/mediagoblin.example.org/mediagoblin/bin -type f -exec chmod 750 {} \;
 
 .. note::
-   
+
    If you see an Nginx placeholder page, you may need to remove the
    Nginx default configuration, or explictly set a ``server_name``
    directive in the Nginx config.