Update Blog “open-sourcing-workshops-on-demand-part2-deploying-the-backend”

Author: pattdepanick

content/blog/open-sourcing-workshops-on-demand-part2-deploying-the-backend.md

@@ -79,9 +79,9 @@ In order to setup the backend server, you will need:
 
 **Note**: In order to support 100 concurrent users, you need:    
 
-   * 2 cpus or more machine
-   * 128 GB of RAM 
-   * 500 GB of storage 
+* 2 cpus or more machine
+* 128 GB of RAM 
+* 500 GB of storage 
 
 We are currently using an HPE ProLiant DL360 Gen10 server on our different production sites.
 
@@ -95,9 +95,10 @@ install$ cd wod-backend/
 ```
 
 * Examine default installation parameters and adapt when necessary accordingly. Files are self-documented.
-* Look at the following files within ansible/group_vars directory.    
 
-   * `all.yml` file  
+  Look at the following files within ansible/group_vars directory.    
+
+  * `all.yml` file  
 
 ```shellsession
 vi all.yml
@@ -170,7 +171,7 @@ SCRIPTPRIVDIR: "{{ WODPRIVDIR }}/scripts"
 ANSIBLEPRIVDIR: "{{ WODPRIVDIR }}/ansible"
 ```
 
-   * `wod-backend` file  
+* `wod-backend` file  
 
 ```shellsession
 vi wod-backend
@@ -227,7 +228,7 @@ DATAVISUPORT1-WKSHP-DataVisu101: 22101
 DATAVISUPORT2-WKSHP-DataVisu101: 22131
 ```
 
-   * `wod-system` file
+* `wod-system` file
 
 ```shellsession
 vi wod-system
@@ -261,7 +262,7 @@ WODFEAPIUSER: moderator
 WODFEAPIPWD: MotDePasseCompliquéAussi125!!!##
 ```
 
-See the example below for a backend server.
+ See the example below for a backend server.  
 
 ### Backend installation process:
 
@@ -277,19 +278,22 @@ See the example below for a backend server.
 * Installs minimal required (`ansible, git, jq, openssh server, npm`)
 * Creates an admin user as defined upper (default is `wodadmin`) with sudo rights
 * Calls the `install-system-common.sh` script that performs the following tasks:    
+
   * Cleanup    
   * Github repos cloning (leveraging install.repo file) : public Backend and public Private repos    
   * Create ssh keys for wodadmin    
   * Creates GROUPNAME variables    
   * Creates Ansible inventory files       
 * Calls the `install_system.sh` script with the type (backend, frontend, etc..) that performs the following tasks:    
+
   * Install the necessary stack based on selected type    
   * Create a `wod.sh` script in `wod-backend` directory to be used by all other scripts    
   * Source the `wod.sh` file     
   * Setup Ansible-galaxies (`community.general` and `posix`)    
   * Setup Ansible and call the playbook `install_<type>.yml` followed by the `ansible\_check\_<type>.yml`    
 
 At the end of the installation process:
+
 * you will have a JupyterHub server running on port 8000    
 * You will get a new `wodadmin` user (Default admin)    
 * You will get a set of 20 students (Default value)    
@@ -317,14 +321,15 @@ The principle remains similar, with a few differences explained below.
 * Create an `install.priv` file located in `install` directory when using a private repo (consider looking at [install.repo](https://github.com/Workshops-on-Demand/wod-backend/blob/main/install/install.repo) file for a better understanding of the variables).
 * Define the WODPRIVREPO and WODPRIVBRANCH variables as follows:    
 
-  * `WODPRIVBRANCH="main" `     
+  * `WODPRIVBRANCH="main"`     
   * `WODPRIVREPO="[email protected]:Account/Private-Repo.git wod-private"`    
 
 **Note:** When using a token
 
 Please refer to the following [url](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) to generate a `token` file in `install` directory of WoD-backend:
 
 * Edit the `install.priv` file located in `install` directory of WoD-backend:  
+
   * Create line before variable declaration: ``token=`cat $EXEPATH/token` ``    
   * Use the token in the url WODPRIVREPO="git clone https://user:[email protected]/Account/wod-private.git wod-private"