boltless.me
targeting
master
from
sl/knotmirror
knotmirror is an external service that is intended to be used by appview. It will ingest all known git repos and provide xrpc methods to inspect them, so appview won't need to fetch individual knots on every page render.
Signed-off-by: Seongmin Lee git@boltless.me
tangled.org
knotBackoff and reachability test
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
This file has not been changed.
KnotMirror is an external service that is intended to be used by
appview. It will ingest all known git repos and provide xrpc methods to
inspect them, so appview won't need to fetch individual knots on every
page render.
Using postgres exclusively instead of sqlite to support A LOT of
concurrent writes.
Signed-off-by: Seongmin Lee <git@boltless.me>
KnotMirror is an external service that is intended to be used by
appview. It will ingest all known git repos and provide xrpc methods to
inspect them, so appview won't need to fetch individual knots on every
page render.
Using postgres exclusively instead of sqlite to support A LOT of
concurrent writes.
Signed-off-by: Seongmin Lee <git@boltless.me>
KnotMirror is an external service that is intended to be used by
appview. It will ingest all known git repos and provide xrpc methods to
inspect them, so appview won't need to fetch individual knots on every
page render.
Using postgres exclusively instead of sqlite to support A LOT of
concurrent writes.
Signed-off-by: Seongmin Lee <git@boltless.me>
knotmirror is an external service that is intended to be used by
appview. It will ingest all known git repos and provide xrpc methods to
inspect them, so appview won't need to fetch individual knots on every
page render.
Signed-off-by: Seongmin Lee <git@boltless.me>
no need for more flags IMO
The intention was to make knotmirror service embeddable by allowing full config as an input of knotmirror.Run(). And while doing that, I thought it would be nice if we can have cli flags to override the config.
what does the Crawler do?
Crawler came from tap.Crawler which periodically schedules the resync job for known repos. As we don't have a way to check the repository state, I leave the implementation blank. It isn't strictly necessary and not valuable to implement in current structure. See TAN-283 on how I am going to check repository sync state.
So yeah, it does nothing right now.
do we need the func and the global?
Uh, I think I lost one of my changes while reordering commits... I will fix that.
would appreciate if the stack were cleaned up to remove such mutations as it is slightly hard to follow.
will do.
knotmirror/knotstream/slurper.go:331
I think this is counting nanoseconds instead of seconds. Intentional?
good catch. Seems like I brought a bug from indigo/relay. Sorry for that, should check more carefully.
knotmirror is an external service that is intended to be used by
appview. It will ingest all known git repos and provide xrpc methods to
inspect them, so appview won't need to fetch individual knots on every
page render.
Signed-off-by: Seongmin Lee <git@boltless.me>
cmd/knotmirror/main.go:49we can have the entire thing config'd via env vars, no need for more flags IMO.knotmirror/crawler.go:11: what does the Crawler do?knotmirror/models/models.go:45-63: do we need the func and the global?will post this as a preliminary review, and do a further code review shortly, i can see that PRs above this stack mutate the knotmirror modules, such as the postgres migration. would appreciate if the stack were cleaned up to remove such mutations as it is slightly hard to follow.