zecfoundation
/
infra-monitoring-kuma
mirror of https://github.com/ZcashFoundation/infra-monitoring-kuma.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
7 Commits 3 Branches 2 Tags 211 KiB
Commit Graph

7 Commits

Author SHA1 Message Date
Gustavo Valverde a0aa4faa4a ref(workflows): align workflows with `zfnd` standards 2024-07-29 18:05:36 +01:00
Gustavo Valverde 81b47a200e
docs: new decision for adding a monitoring tool (#2) 
* docs: new decision for adding a monitoring tool

* docs(adr): fix title

* imp(adr): add more consequences

* Update docs/decisions/2024-07-12-monitoring-tool.md

Co-authored-by: Pili Guerra <mpguerra@users.noreply.github.com>

---------

Co-authored-by: Pili Guerra <mpguerra@users.noreply.github.com>
 2024-07-17 11:05:07 +01:00
Gustavo Valverde 4652db30ab fix(deploy): do not allow public access to prod 2024-07-15 14:47:58 +01:00
Gustavo Valverde 1e2760113f fix(dependabot): use correct docker directory 2024-07-15 14:40:44 +01:00
Gustavo Valverde 16a3f21f39
add: uptime-kuma and workflow files (#1) 
* add: uptime-kuma and workflow files

* imp: use latest uptime kuma for better DB management

* ref(deploy): allow an external `mariadb` database

* fix(db): patch `knex_init_db.js` file

* fix(runtime): avoid spawning zombie processes

* chore: do not commit `trunk` linting confs

* fix(actions): permissions

* imp(deploy): use secrets from GCP secret manager
 2024-07-15 10:53:05 +01:00
Gustavo Valverde 7dac323258 feat(docs): add a `decisions` folder with ADR 
An architectural decision record (ADR) is a document that describes a choice the team makes about a significant aspect of the software architecture they’re planning to build. Each ADR describes the architectural decision, its context, and its consequences. ADRs have states and therefore follow a lifecycle
 2024-07-12 16:34:37 +01:00
Gustavo Valverde fae1e99526 add: main files 2024-06-28 08:26:18 -04:00