Skip to content

Commit

Permalink
updated docs
Browse files Browse the repository at this point in the history
  • Loading branch information
f-w committed Dec 17, 2024
1 parent 792e554 commit f7f0a7f
Show file tree
Hide file tree
Showing 7 changed files with 36 additions and 3 deletions.
1 change: 1 addition & 0 deletions docs/.vuepress/config.js
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,7 @@ export default defineUserConfig({
'/docs/config-oidc/',
'/docs/config-certificates/',
'/docs/config-queue/',
'/docs/config-logging/',
],
},
{
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/api/overview.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
permalink: /docs/api-overview/
prev: /docs/config-queue/
prev: /docs/config-logging/
---

# API Overview
Expand Down
24 changes: 24 additions & 0 deletions docs/docs/config/logging.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
permalink: /docs/config-logging/
next: /docs/api-overview/
---

# Logging

Besides request logging using morgan [middleware](middleware.md), _NotifyBC_ also generates application log. Application log has following levels in descending severities

1. fatal
2. error
3. warn
4. log
5. debug
6. verbose

By default the first 4 logging levels are output to console. To override the defaults, set the `loggingLevels` config in _src/config.local.js_. For example, to include debug logs

```js
module.exports = {
// ...
loggingLevels: ['fatal', 'error', 'warn', 'log', 'debug'],
};
```
1 change: 0 additions & 1 deletion docs/docs/config/queue.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
---
permalink: /docs/config-queue/
next: /docs/api-overview/
---

# Queue
Expand Down
2 changes: 2 additions & 0 deletions docs/docs/meta/acknowledgments.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ few services. Credit goes to their contributors. Notably
- [MongoDB](https://www.mongodb.com/)
- [NodeMailer](https://nodemailer.com/)
- [JMESPath](https://jmespath.org/)
- [BullMQ](https://docs.bullmq.io/)
- [Redis](https://redis.io/)
- [Vue](https://vuejs.org/)
- [Vuetify](https://vuetifyjs.com/)
- [iframe-resizer](https://iframe-resizer.com/)
Expand Down
7 changes: 7 additions & 0 deletions docs/docs/miscellaneous/disaster-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,10 @@ Under disastrous circumstances, however, entire HA cluster may fail. Recovery sh
1. MongoDB
2. Redis
3. API server

Notes

- MongoDB holds persistent data. When recovering MongoDB, data needs to be recovered. If data is corrupted, restore from backup.
- If MongoDB is the only failed component, after recovery, the other two components don't need to be restarted.
- Redis doesn't hold persistent data. When recovering Redis, data doesn't need to be recovered.
- After recovering Redis, API server needs to be restarted.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "notify-bc",
"version": "5.1.2",
"version": "6.0.0",
"dbSchemaVersion": "0.9.0",
"description": "A versatile notification API server",
"author": "f-w",
Expand Down

0 comments on commit f7f0a7f

Please sign in to comment.