Skip to content

Commit 4f6821d

Browse files
committed
Update Blog “open-sourcing-workshops-on-demand-part2-deploying-the-backend”
1 parent f53e165 commit 4f6821d

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

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

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -53,12 +53,12 @@ Here's a quick look at what can be found in each:
5353
![](/img/wod-blogserie2repos.png "Workshops-on-Demand repositories")
5454

5555
It provides:
56-
A complete JupyterHub server with some addons (additional Jupyterhub kernels, Ansible galaxies, and PowerShell libraries) on your system, ready to host Workshops-on-Demand that you can find here.
57-
A postfix server used for the procmail API
58-
An Ansible engine to allow automation
59-
A fail2ban service
60-
An Admin user to manage everything
61-
A set of scripts to handle different tasks such as:
56+
* A complete JupyterHub server with some addons (additional Jupyterhub kernels, Ansible galaxies, and PowerShell libraries) on your system, ready to host Workshops-on-Demand that you can find here.
57+
* A postfix server used for the procmail API
58+
* An Ansible engine to allow automation
59+
* A fail2ban service
60+
* An Admin user to manage everything
61+
* A set of scripts to handle different tasks such as:
6262
o Notebooks deployment
6363
o Jupyterhub compliancy
6464
o Users compliancy
@@ -71,26 +71,26 @@ Before cloning the backend repository, you will need to prepare the server th
7171
###### Prerequesites:
7272

7373
1. In order to setup the backend server, you will need:
74-
A fresh OS install on physical / virtualized server running Ubuntu 20.04 or Centos 7.9 leveraging any deployment mechanism of your choice.(e.g. iLO, vagrant, etc.). You may even use this vagrant file to automatically generate a complete setup leveraging vagrant, libvirt and QEMU/KVM.
75-
A Linux account with sudo priviledges on your Linux distro. Name it install
74+
* A fresh OS install on physical / virtualized server running Ubuntu 20.04 or Centos 7.9 leveraging any deployment mechanism of your choice.(e.g. iLO, vagrant, etc.). You may even use this vagrant file to automatically generate a complete setup leveraging vagrant, libvirt and QEMU/KVM.
75+
* A Linux account with sudo priviledges on your Linux distro. Name it install
7676
Note: In order to support 100 concurrent users, you need:
77-
2 cpus or more machine
78-
128 GB of RAM
79-
500 GB of storage
77+
* 2 cpus or more machine
78+
* 128 GB of RAM
79+
* 500 GB of storage
8080

8181
We are currently using an HPE ProLiant DL360 Gen10 server on our different production sites.
8282

8383
2. When done with OS installation and preparation
84-
From the WoD-backend server (aka JupyterHub server), as the install user, you will need to clone the repo first.
84+
* From the WoD-backend server (aka JupyterHub server), as the install user, you will need to clone the repo first.
8585

8686
```
8787
install$ git clone https://github.com/Workshops-on-Demand/wod-backend.git
8888
install$ cd wod-backend/
8989
```
90-
Examine default installation parameters and adapt when necessary accordingly. Files are self-documented.
91-
Look at the following files within ansible/group_vars directory.
90+
* Examine default installation parameters and adapt when necessary accordingly. Files are self-documented.
91+
* Look at the following files within ansible/group_vars directory.
9292

93-
`all.yml` file
93+
*`all.yml` file
9494

9595
```shellsession
9696
vi all.yml

0 commit comments

Comments
 (0)