|
|
16640ac022
|
Restart nidus-sync on failure
|
2026-03-11 15:52:01 +00:00 |
|
|
|
f9fee85606
|
Create needed data directories for nidus-sync on deploy
|
2026-02-18 21:30:06 +00:00 |
|
|
|
31335d19f7
|
Create separate prod/staging nidus-sync sops environments
|
2026-02-18 06:09:50 +00:00 |
|
|
|
f86239a8ce
|
Make RMO domain name a config option
|
2026-02-18 05:07:22 +00:00 |
|
|
|
f0e9d04dc1
|
Make nidus-sync domain a variable
The beginning of separating out staging
|
2026-02-17 17:38:42 +00:00 |
|
|
|
d6fc5502f6
|
Add report/sync URLs for nidus
|
2026-01-12 14:12:56 +00:00 |
|
|
|
1055f382fc
|
Move nidus sync to its own backup buckets
When doing the restore recently it seemed likely that there were
conflicts with sharing the buckets.
|
2026-01-12 14:12:12 +00:00 |
|
|
|
423c1e6d9f
|
Working tegola delpoy
This uses the data from Bonn, Germany which I downloaded from
https://github.com/go-spatial/tegola-example-bonn/tree/main
|
2025-11-14 18:58:42 +00:00 |
|
|
|
f3b8602f30
|
Actually serve sync.nidus.cloud with the new config.
|
2025-11-11 17:57:35 +00:00 |
|
|
|
44c0d83bf6
|
Add nidus-sync production module
This will allow me to keep nidus-sync stable while continuing to do
development on this same server on a different port.
|
2025-11-11 17:24:41 +00:00 |
|
