Ask Bjørn Hansen 42ce22e83e adjust cache-control for history api ...

it seems like there's a bug in the data calculations so many
servers get the too long maximum cache time; make it shorter
while we debug

2025-06-27 17:48:40 +08:00

chdb

dns queries: set cache-control header

2025-02-23 09:48:56 -08:00

cmd

Log version on startup

2023-11-21 12:24:02 -08:00

logscores

scores: full_history option for internal clients

2024-01-20 23:21:21 -07:00

ntpdb

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

scripts

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

server

adjust cache-control for history api

2025-06-27 17:48:40 +08:00

.dockerignore

wip

2023-05-07 00:01:00 -07:00

.drone.yml

Update Go to 1.24 + dependencies

2025-03-08 10:21:44 -08:00

.gitignore

Build tools

2023-07-08 22:09:31 -07:00

.goreleaser.yml

Update Go and dependencies

2024-12-27 17:38:58 -08:00

Dockerfile

Upgrade Go & dependencies

2025-01-17 21:03:31 -08:00

go.mod

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

go.sum

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

LICENSE

Start repository

2023-04-18 21:54:54 -07:00

main.go

wip

2023-05-07 00:01:00 -07:00

Makefile

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

query.sql

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

schema.sql

Update schema for monitors v4; use go tool

2025-06-21 03:49:02 -07:00

sqlc.yaml

scores: csv handler

2023-12-10 21:02:04 -08:00

Description

No description provided

MIT 449 KiB

Languages

Go 98.5%

Shell 0.7%

Dockerfile 0.5%

Makefile 0.3%