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
Chronos consists of a [Node](https://nodejs.org/en/) module available through the
100
-
[npm registry](https://www.npmjs.com/) and a lightweight [Electron](https://electronjs.org/) desktop application.
92
+
[npm registry](https://www.npmjs.com/) and a lightweight [Electron](https://electronjs.org/) desktop application.-->
101
93
102
-
## Usage
94
+
#Containerized Applications Using Docker
103
95
104
96
IMPORTANT: Give your containers the same names you use for arguments for microservice names. Read more about it under the INSTALLATION section below.
105
97
@@ -118,24 +110,8 @@ volumes:
118
110
119
111
\*Note: This module leverages the features of [systeminformation](https://systeminformation.io/).
120
112
121
-
#### Node module
122
-
123
-
To begin, install the [Chronos](https://www.npmjs.com/package/chronos-microservice-debugger4) node module within each microservice of your application using the
Once installed, write the following two lines at the top of each microservice's server file:
131
-
132
-
Then add a route handler for all incoming requests:
133
-
134
-
The cmd.microCom handler function logs communication and health data to a user-provided database. This is to ensure that your private data stays private. We currently support MongoDB and SQL/PostgreSQL databases.
135
-
136
-
cmd.microCom takes six parameters. You can enter the arguments as individual strings or as an array.
137
113
138
-
The parameters are:
114
+
## Configuration Setup
139
115
140
116
-[1] microserviceName: To identify the microservice (i.e. "payments").
141
117
- Make sure this name matches your container name. More details more below (param #6).
@@ -154,38 +130,8 @@ The parameters are:
154
130
- IMPORTANT: When starting up the container, give it the same name that you used for the microservice, because the middleware finds the correct container ID of your container by matching the container name to the microservice name you input as 1st argument.
155
131
- Don't forget to bind mount to Docker socket. See NEW FEATURE section above.
Additionally, the repo includes a test suite of microservices utilizing the Chronos node module so that their communication, health, and container data can be logged. You can then visualize the data with the Electron app.
191
137
@@ -195,30 +141,36 @@ Refer to the [README](https://github.com/oslabs-beta/Chronos/tree/docker/microse
195
141
196
142
#### Electron desktop application
197
143
198
-
After installing the node module in each microservice, download the Electron desktop application from the public [Chronos](https://github.com/oslabs-beta/Chronos) repo.
144
+
After installing the node module in each microservice, download the Electron desktop application from the public [Chronos]() repo.
199
145
200
146
Inside the downloaded directory, install all dependencies using the `npm install` command followed by the `npm start` command to start the Electron desktop application.
201
147
202
148
## Contributing
203
149
204
-
Chronos hopes to inspire an active community of both users and developers. For questions, comments, or contributions, please submit a pull request.
150
+
Development of Chronos is open source on GitHub through the tech accelerator umbrella OS Labs, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving Chronos.
0 commit comments