Skip to content

Commit 0b92368

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

File tree

2 files changed

+37
-0
lines changed

2 files changed

+37
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: "Open Sourcing Workshops-on-Demand part 5: Deploying and Managing API-DB
3+
server"
4+
date: 2025-06-24T09:52:09.975Z
5+
author: Frederic Passeron
6+
authorimage: /img/frederic-passeron-hpedev-192.jpg
7+
disable: false
8+
---
9+
In previous articles of this series dedicated to the [open sourcing of our Workshops-on-Demand project](https://developer.hpe.com/blog/willing-to-build-up-your-own-workshops-on-demand-infrastructure/), I covered the reasons why we open sourced the project and how we did it. I also explained in details how you could install your own Workshops-on-Demand backend server. I also took the time to detail the automation that was hosted on this backend server. I also described to you the management of this backend server. This is what is often referred to as Day2 operations. I plan now to explain how to deploy and manage the API-DB server.
10+
11+
The following image is describing the different interactions existing between the different components of the wod architecture.
12+
13+
![](/img/howto-wod-1.png "WOD Architecture")
14+
15+
16+
17+
18+
19+
## How to deploy your own api-db server...
20+
21+
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.
22+
23+
I will start with the simpliest scenario: A public-only approach. Then we will dive into the specificities related the private approach.
24+
25+
### Public-only Deployment: No private backend nor private workshops
26+
27+
**Important Note:**
28+
29+
**This part is compulsory for any type of deployment. Public only or public + private.**
30+
31+
First, you need a repository to clone. The Workshops-on-Demand GitHub projects can be found [here](https://github.com/Workshops-on-Demand/). We have packaged the solution in several Github repos. Each repository handles a specific role in the overall architecture. We recently introduced a wod-install repository.
32+
33+
This repository is the most important one when it comes to deploying the wod infrastructure. It contains all the installation scripts for every part of the solution.
34+
35+
Here's a quick look at what can be found in each:
36+
37+
![](/img/wod-blogserie2-2repos.png "WOD repositories")

static/img/howto-wod-1.png

650 KB
Loading

0 commit comments

Comments
 (0)