alpha
Login
or
Join now
alice.pds.demo.boltless.dev
/
core
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
2
Pulls
1
Pipelines
core
/
knotserver
4 folders
7 files
at
caf7b4ca00102045e90feeeb96fd3031cdbbccef
Anirudh Oppiliappan
knotserver: /init and /user endpoints
2y ago
caf7b4ca
config
knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.
2 years ago
db
knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.
2 years ago
git
knotserver: better config management and /repo/new
2 years ago
jsclient
knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.
2 years ago
file.go
all: rename package
2 years ago
git.go
all: rename package
2 years ago
handler.go
knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.
2 years ago
http_util.go
knotserver: fix a bunch of things
2 years ago
middleware.go
knotserver: get/put ssh keys
2 years ago
routes.go
knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.
2 years ago
util.go
knotserver: remove unused code
2 years ago