Public
Readme
This is a lightweight Blob Admin interface to view and debug your Blob data.
Versions 0-17 of this val were done with Hono and server-rendering. Versions 18+ were generated with Townie and use client-side React.
To use this val, fork it to your account. Authentication is handled by @stevekrouse/lastlogin, so only the owner of the val will be able to see and edit their own blobs.
Val Town is a social website to write and deploy JavaScript.
Build APIs and schedule functions from your browser.
v16 was merged from the PR "add upload button" by pomdtr
stevekrouse-blob_admin.web.val.run
Updated: December 13, 2024
Instead of instructing the user to fork the val, why not suggest the user to create a new val referencing your own ?
It would allow the user to automatically get update from your, or control them using the version query param.
Excellent idea! That's how @rodrigotello/hnFollow works.
This way is slightly easier to customize, that way is slightly easier to manage updates.
In theory, Val Town could help users manage forks like Github does:
Or even notify users that they should "pull" from the remote val because it has new changes.
The question of when to use something as a dependency vs as a fork is a fascinating one. I'm eager to see what patterns emerge
I see importing as an installation method a val to my val.town account, while forking is just copying a specific version of a val.
I can see myself using, it depends as if I see myself as a user or a contributor.
Even for the same val, I can see myself having my prod endpoint and my dev endpoint.
comments really need an edit button 😅
It's not working anymore. I'm getting an error message. "message": "{"statusCode":500,"error":"Internal Server Error","message":"Failed to create Turso DB: Namespace store has shutdown"}",
Sorry about that @loshmyy. We haven't seen that error message before. Is everything working properly now?
@pomdtr
And a like button too, even reply or quote button.
PS. I just notice I can 'edit' the comment easily now.
@stevekrouse Everything is working now, thank you!
For UI centric products, I would fork and customize or to contribute a change. With deps I'm specifically looking to use that version. forks are easier to view have updates vs dep generally to me feel like a chore I have to do as maintenance. At min for security patches from socket.io.
but never thought about it as such. This is very fascinating indeed!
Hello, Steve - I just forked the blob_admin, logged in using Google...and ran into an "Internal Server Error". Any ideas why and how to ged rid of it?
The browser complains "Failed to load resource: the server responded with a status of 500 ()" for resource "https://rozek-blob_admin.web.val.run/"
Hey @rozek, thanks for writing in! I was able to get that same error when logging in with a different email address than the one tied to my Val Town account. I then popped open my request logs, saw the error message, and clicked on the line of code, and fixed it. (It took two fixes.) Hope that's your issue and you can fork it again to get it working!
For next time, be sure to check out your request logs. You could even pop open Townie to get help fixing it. And then you can send me a pull request with your fix :)
Here's a video of me reproducing, finding, and fixing the bug: https://share.cleanshot.com/cMrD7kdl
@stevekrouse cool, how to fix bugs within val.town - thanks for your effort and the video! Unfortunately, your blob_admin does not seem to like me: I forked the new blob_admin, tried it...and failed again. I've taken two screenshots for demonstration: