You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/dev/README.md
+64-58Lines changed: 64 additions & 58 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,40 +6,8 @@ OpenCRVS can be deployed either:
6
6
7
7
***Manually** (using Helm and CLI commands), see [README-on-existing-cluster](README-on-existing-cluster.md) or
8
8
***Automatically** (using the provided GitHub Action Workflows).
9
-
10
9
---
11
10
12
-
# Prerequisites
13
-
14
-
Before starting the deployment, ensure the following requirements are met:
15
-
16
-
**1. Virtual Machine resources**
17
-
18
-
* Minimum: **8 CPU cores, 16 GB RAM, 50 GB SSD**.
19
-
20
-
**2. Operating System**
21
-
22
-
* VM is running **Ubuntu 24.04 LTS**.
23
-
24
-
**3. Networking and Domain Configuration**
25
-
26
-
* The VM must have a **public IP address** and (or) ports **80** and **443** must be accessible.
27
-
* A **valid domain name** must be configured and point to the VM.
28
-
* Required DNS records:
29
-
30
-
* An **A record** pointing the primary domain to the VM IP (e.g., `opencrvs.example.com`).
31
-
* A **wildcard A record** (e.g., `*.opencrvs.example.com`) or individual subdomains pointing to the same VM IP.
32
-
* These settings are required for **Traefik** to issue valid SSL certificates using Let’s Encrypt (`http-01` challenge).
33
-
34
-
> See the [OpenCRVS documentation on DNS setup](https://documentation.opencrvs.org/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.5-setup-dns-a-records#domain-a-records) for details.
35
-
36
-
> If you don't have public IP Address please follow guide "How to run traefik with self-signed SSL Certificate", see [TODO](#link-goes-here)
37
-
38
-
**4. Create provisioning User**
39
-
40
-
* The VM must be provisioned with an SSH user account according to [Provision Your Server Nodes with SSH Access](https://documentation.opencrvs.org/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.1-provision-your-server-nodes-with-ssh-access).
41
-
42
-
---
43
11
44
12
# Deployment Package Contents
45
13
@@ -73,6 +41,35 @@ The deployment package includes the following components:
73
41
* MOSIP integration version: `latest`
74
42
75
43
44
+
---
45
+
46
+
# Prerequisites
47
+
48
+
Before starting the deployment, ensure the following requirements are met:
49
+
50
+
**1. Virtual Machine resources**
51
+
52
+
* Minimum: **8 CPU cores, 16 GB RAM, 50 GB SSD**.
53
+
54
+
**2. Operating System**
55
+
56
+
* VM is running **Ubuntu 24.04 LTS**.
57
+
58
+
**3. Networking and Domain Configuration**
59
+
60
+
* The VM must have a **public IP address** and (or) ports **80** and **443** must be accessible.
61
+
* A **valid domain name** must be configured and point to the VM.
62
+
* Required DNS records:
63
+
64
+
* An **A record** pointing the primary domain to the VM IP (e.g., `opencrvs.example.com`).
65
+
* A **wildcard A record** (e.g., `*.opencrvs.example.com`) or individual subdomains pointing to the same VM IP.
66
+
* These settings are required for **Traefik** to issue valid SSL certificates using Let’s Encrypt (`http-01` challenge).
67
+
68
+
> See the [OpenCRVS documentation on DNS setup](https://documentation.opencrvs.org/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.5-setup-dns-a-records#domain-a-records) for details.
69
+
70
+
> If you don't have public IP Address please follow guide "How to run traefik with self-signed SSL Certificate", see [TODO](#link-goes-here)
71
+
72
+
---
76
73
77
74
# Deploy OpenCRVS with GitHub Actions Workflows
78
75
@@ -88,27 +85,8 @@ You will need to provide the following values while installation multiple times:
88
85
* Environment name: `<env name>`
89
86
---
90
87
91
-
## 1. Bootstrap GitHub Self-Hosted Runner
92
-
93
-
The self-hosted runner must be installed on the single VM (or master node).
1. If successful, you will see a confirmation message:
105
-
```
106
-
✅ Runner '....-runner' is installed and started!
107
-
```
108
-
2. In your GitHub repository, navigate to **Settings → Actions → Runners** and verify that the runner appears as a self-hosted runner.
109
-
110
88
---
111
-
## 2. Create a GitHub environment
89
+
## 1. Create a GitHub environment
112
90
113
91
* Checkout forked repository into any folder on your laptop
114
92
```
@@ -122,8 +100,36 @@ The self-hosted runner must be installed on the single VM (or master node).
122
100
```
123
101
yarn environment:init
124
102
```
103
+
* Go to GitHub and verify the newly created environment
104
+
105
+
106
+
## 2.1. Bootstrap GitHub Self-Hosted Runner
107
+
108
+
The self-hosted runner must be installed on the single VM (master node). The VM must be provisioned with an SSH user account according to [Provision Your Server Nodes with SSH Access](https://documentation.opencrvs.org/setup/3.-installation/3.3-set-up-a-server-hosted-environment/3.3.1-provision-your-server-nodes-with-ssh-access).
109
+
110
+
> NOTE: On previous step environment configuration script left correct command as output.
At environment creation phase environment files are stored into `environments/<env name>` folder. Navigate to this folder and update files one by one. Folder contains configuration for the following helm charts:
179
-
- traefik, Usually helm chart doesn't require updates.
180
-
-opencrvs dependencies, Usually helm chart doesn't require updates.
181
-
- opencrvs application, Usually helm chart doesn't require updates.
184
+
At environment creation phase helm chart values files are stored into `environments/<env name>` folder. Usually default configuration properties are sufficient forfirst deployment:
0 commit comments