feat: new /memo badge built on Vercel KV #636
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created a new badge called
Memo Badge
. In short, you may update a memo badge with your own cron job or ci job or whatever possible method.It's a further step of the previous
/https
badge that enables more usages, and more simpler to use with:/https
is an extension interface to badgen.net, you can create a badge service with your own endpoint. (e.g. tickgit)./memo
is an extension, extending badgen.net with memory. Now you can not only read a badge from badgen.net, you can also write to it!I have been thinking about this badge for a long time, firstly I built it with Cloudflare KV, but it's like two different pieces glued together, this feeling bugs me all the time. Then Vercel announced KV, that's what I'm looking for! And finally I got some time to made the upgrade (after the migration to Next.js 13).
Checkout https://badgennet-git-migrate-memo-badgen.vercel.app/memo