Skip to content

Commit a1a51eb

Browse files
committed
Update Blog “open-sourcing-workshops-on-demand-part-5-deploying-and-managing-api-db-server”
1 parent 0b92368 commit a1a51eb

File tree

1 file changed

+51
-5
lines changed

1 file changed

+51
-5
lines changed

content/blog/open-sourcing-workshops-on-demand-part-5-deploying-and-managing-api-db-server.md

Lines changed: 51 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,6 @@ The following image is describing the different interactions existing between th
1212

1313
![](/img/howto-wod-1.png "WOD Architecture")
1414

15-
16-
17-
18-
1915
## How to deploy your own api-db server...
2016

2117
As explained in the previous [article](https://developer.hpe.com/blog/willing-to-build-up-your-own-workshops-on-demand-infrastructure/), the project is split into multiple repositories from the architectural and public / private aspects. The architecture is divided between the frontend and backend. The project admins will need to decide whether they are willing to develop and propose public-only content to the participants or add any proprietary and private content.
@@ -34,4 +30,54 @@ This repository is the most important one when it comes to deploying the wod inf
3430

3531
Here's a quick look at what can be found in each:
3632

37-
![](/img/wod-blogserie2-2repos.png "WOD repositories")
33+
![](/img/wod-blogserie2-2repos.png "WOD repositories")
34+
35+
36+
37+
**[wod-notebooks](https://github.com/Workshops-on-Demand/wod-notebooks):** Public Workshops-on-Demand based on Jupyter Notebooks.
38+
39+
* You can test them live at <https://hackshack.hpedev.io/workshops>
40+
41+
**[wod-install](https://github.com/Workshops-on-Demand/wod-install):** Installer part of the Workshops-on-Demand project.
42+
43+
**[wod-backend](https://github.com/Workshops-on-Demand/wod-backend):** Back-end part of our Workshops-on-Demand setup.
44+
45+
**[wod-frontend](https://github.com/Workshops-on-Demand/wod-frontend):** Frontend part of the Workshops-on-Demand project.
46+
47+
* Based on NGINX and NodeJS technologies, it provides the participtants' Registration Portal used to enable booking of the workshops.
48+
49+
**[wod-api-db](https://github.com/Workshops-on-Demand/wod-api-db):** Workshops-on-Demand registration portal application
50+
51+
* Open API 3.0 based api used to manage the Workshops-on-Demand project. It also provides a database hosting the different status of participants, workshops, and students.
52+
53+
**[wod-private](https://github.com/Workshops-on-Demand/wod-private):** Example Private configuration for Workshops-on-Demand (WoD).
54+
55+
**[wod-frontend-private](https://github.com/Workshops-on-Demand/wod-frontend-private):** Private Frontend part of the Workshops-on-Demand project.
56+
57+
**[wod-api-db-private](https://github.com/Workshops-on-Demand/wod-api-db-private):** Workshops-on-Demand registration portal application
58+
59+
* This provide examples for creating your own cutomization layer on top of the public standard WoD Backend / wod Notebooks content. Do not put any confidential data here as this is a public repository!
60+
61+
**Note**: There are now 7 repositories available for now.
62+
63+
It provides:
64+
65+
* 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.
66+
* A postfix server used for the procmail API
67+
* An Ansible engine to allow automation
68+
* A fail2ban service
69+
* An Admin user to manage everything
70+
* A set of scripts to handle different tasks such as:
71+
72+
* Notebooks deployment
73+
* Jupyterhub compliancy
74+
* Users compliancy
75+
* Security Management
76+
77+
#### Backend server preparation:
78+
79+
Before cloning the backend repository, you will need to prepare the server that will host the backend features. When ready, you will proceed with the cloning and then the installation process.
80+
81+
##### Prerequesites:
82+
83+
In order to setup the backend server, you will need:

0 commit comments

Comments
 (0)