Tangled knot that runs on Cloudflare Workers

Star

17

Fork

0

Atom

Configure Feed

Issues

Pull Requests

Commits

Tags

Feed URL

Select the types of activity you want to include in your feed.

Star

17

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

Pulls

Pipelines

Rust

96.0%

JavaScript

3.0%

Shell

0.6%

Nix

0.2%

Dockerfile

0.2%

main

op/tests

op/knot-artifacts

op/ci

op/artifacts-crate

op/qzwyxwtysxsr

No tags found

22

6

0

Code

Clone this repository

Use permalink

HTTPS

https://tangled.org/oppi.li/naut https://tangled.org/did:plc:yxhmsmeoxfkkmc546cevsx4m getComputedStyle(s).display !== 'none').textContent)" class="px-3 py-2 text-gray-500 hover:text-gray-700 dark:text-gray-400 dark:hover:text-gray-200" title="Copy to clipboard"

SSH

git@knot2-artifacts.anirudh-s-account.workers.dev:oppi.li/naut git@knot2-artifacts.anirudh-s-account.workers.dev:did:plc:yxhmsmeoxfkkmc546cevsx4m getComputedStyle(s).display !== 'none').textContent)" class="px-3 py-2 text-gray-500 hover:text-gray-700 dark:text-gray-400 dark:hover:text-gray-200" title="Copy to clipboard"

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz

Download .zip

crates

1 week ago

scripts

1 week ago

worker

1 week ago

.gitignore

1 week ago

Cargo.lock

1 week ago

Cargo.toml

1 week ago

flake.lock

1 week ago

flake.nix

1 week ago

readme.txt

1 week ago

Commits 22

Merge op/knot-artifacts: knot-artifacts: split artifacts into its own crate

:not(:empty):not(:empty)]:before:content-['·'] [&>:not(:empty):not(:empty)]:before:mx-1 [&>:not(:empty)~:not(:empty)]:before:select-none">

27eaeb1e

oppi.li

1 week ago

main

readme

Signed-off-by: oppiliappan me@oppi.li

oppi.li

1 week ago

knot-artifacts: move the artifacts binding out of the worker

the calls into the cloudflare artifacts binding (create, delete, get, createToken) and the shapes they hand back now live in their own crate with their own error type. it takes the worker's env as a plain JsValue, so it doesn't depend on the worker crate. the worker maps its errors to the same responses as before, and repo create matches AlreadyExists directly instead of a conflict status.