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
## Release candidate with various bug fixes / code refactoring and dependency upgrades
32
32
33
33
### Bug Fixes
34
34
35
-
* Remove width limit on multi-select that caused truncated inputs
36
-
* Fixed tool-tips with HTML elements that weren't being rendered on hover
37
-
* Update webpack to hot reload when changes are made to the scripts
38
-
* Fix graph missing labels by disabling additional minification
39
-
* Fix show reruns button in transactions
40
-
* Fix the redirect to rerun transactions from the popover
35
+
- Remove width limit on multi-select that caused truncated inputs
36
+
- Fixed tool-tips with HTML elements that weren't being rendered on hover
37
+
- Update webpack to hot reload when changes are made to the scripts
38
+
- Fix graph missing labels by disabling additional minification
39
+
- Fix show reruns button in transactions
40
+
- Fix the redirect to rerun transactions from the popover
41
41
42
42
### Code Cleanup
43
43
44
-
* Fix broken Channel test
45
-
* Update tests for dependency upgrades
46
-
* Remove console logs
47
-
* Fix channel success message wording
44
+
- Fix broken Channel test
45
+
- Update tests for dependency upgrades
46
+
- Remove console logs
47
+
- Fix channel success message wording
48
48
49
49
### Updates/Upgrades
50
50
51
-
* Update dependency minor versions and patches for security updates
52
-
* Upgrade dependency major versions where possible
51
+
- Update dependency minor versions and patches for security updates
52
+
- Upgrade dependency major versions where possible
53
53
54
54
### Internal Refactoring
55
55
56
-
* Separate out basicInfo, routes, dataControl, alerts, requestMatching and userAccess controllers from the channelsModal controller into their own files
56
+
- Separate out basicInfo, routes, dataControl, alerts, requestMatching and userAccess controllers from the channelsModal controller into their own files
57
57
58
58
### Enhancements
59
59
60
-
* Add icon to transaction log to indicate that a transaction is a rerun
61
-
* Travis CI runs console against Node Carbon, Dubnium and latest with code coverage
62
-
* Travis CI build status is posted to Jembi slack channel
60
+
- Add icon to transaction log to indicate that a transaction is a rerun
61
+
- Travis CI runs console against Node Carbon, Dubnium and latest with code coverage
62
+
- Travis CI build status is posted to Jembi slack channel
Copy file name to clipboardExpand all lines: README.md
+62-57Lines changed: 62 additions & 57 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@
4
4
5
5
This application provides a web application to configure and manage the [OpenHIM-core component](https://github.com/jembi/openhim-core-js). It provides the following features:
6
6
7
-
* Configure and manage OpenHIM channels
8
-
* View logged transactions
9
-
* Configure clients that can access particular routes
10
-
* Monitor the operations of the OpenHIM application
11
-
* Managing the security infrastructure
12
-
* Importing and exporting OpenHIM server configuration
7
+
- Configure and manage OpenHIM channels
8
+
- View logged transactions
9
+
- Configure clients that can access particular routes
10
+
- Monitor the operations of the OpenHIM application
11
+
- Managing the security infrastructure
12
+
- Importing and exporting OpenHIM server configuration
13
13
14
14
See the [development road-map](http://openhim.org/docs/introduction/roadmap) for more details on what is to come!
15
15
@@ -18,7 +18,9 @@ See documentation and tutorials at [openhim.org](http://openhim.org).
18
18
---
19
19
20
20
## Getting started with the OpenHIM Console
21
+
21
22
### Tech Used
23
+
22
24
- Node: v16.20.2
23
25
- Lerna (microfrontend)
24
26
- Docker
@@ -49,7 +51,7 @@ To run tests:
49
51
npm test
50
52
```
51
53
52
-
**Note:** If you are running from a **microfrontend branch**, be sure to change ``environment`` value inside ```packages/legacy-app/app/config/default.json``` to ``development``. This is when you are running the project locally.
54
+
**Note:** If you are running from a **microfrontend branch**, be sure to change `environment` value inside `packages/legacy-app/app/config/default.json` to `development`. This is when you are running the project locally.
"protocol": "https", // Change the protocol to 'http' when the OpenHIM core API protocol is 'http'. The default OpenHIM core API protocol is 'https'
82
85
"host": "localhost", // change this to the hostname for your OpenHIM-core server (This hostname _MUST_ be publicly accessible)
@@ -90,8 +93,8 @@ Your file should look something like this:
90
93
91
94
Now, navigate to your web server and you should see the OpenHIM-console load (eg. `http://localhost:9000`) and login. The default username and password are:
change the following property from ./packages/legacy-app/app/config/default.json
113
116
114
-
```json
117
+
```json
115
118
{
116
-
"environment": "development"
119
+
"environment": "development"
117
120
}
118
121
```
119
122
@@ -155,89 +158,91 @@ Refer to [this blog](https://developers.redhat.com/blog/2014/05/05/running-syste
155
158
156
159
1. Setup environment
157
160
158
-
Navigate to the infrastructure folder: `infrastructure/centos`
161
+
Navigate to the infrastructure folder: `infrastructure/centos`
159
162
160
-
Provision VM and automatically build RPM package:
163
+
Provision VM and automatically build RPM package:
161
164
162
-
```bash
163
-
vagrant up
164
-
```
165
+
```bash
166
+
vagrant up
167
+
```
165
168
166
-
or without automatic provisioning (useful if you prefer manual control of the process):
169
+
or without automatic provisioning (useful if you prefer manual control of the process):
167
170
168
-
```bash
169
-
vagrant up --no-provision
170
-
```
171
+
```bash
172
+
vagrant up --no-provision
173
+
```
171
174
172
175
1.[Optional] The Vagrant file provisions the VM with the latest source code from master and attempts to compile the RPM package for you. However in the event an error occurs, or if you prefer to have manual control over the process, then you'll need to do the following:
173
176
174
-
* Remote into the VM: `vagrant ssh`
175
-
* Download or sync all source code into VM.
176
-
* Ensure all dependencies are installed.
177
+
- Remote into the VM: `vagrant ssh`
178
+
- Download or sync all source code into VM.
179
+
- Ensure all dependencies are installed.
177
180
178
-
```bash
179
-
npm i && npm i speculate
180
-
```
181
+
```bash
182
+
npm i && npm i speculate
183
+
```
181
184
182
-
* Run speculate to generate the SPEC files needed to build the RPM package.
185
+
- Run speculate to generate the SPEC files needed to build the RPM package.
183
186
184
-
```bash
185
-
npm run spec
186
-
```
187
+
```bash
188
+
npm run spec
189
+
```
187
190
188
-
* Ensure the directory with the source code is linked to the rpmbuild directory - the folder RPMBUILD will use.
191
+
-Ensure the directory with the source code is linked to the rpmbuild directory - the folder RPMBUILD will use.
0 commit comments