This is a lightweight Blob Admin interface to view and debug your Blob data.
Use this button to install the val:
It uses basic authentication with your Val Town API Token as the password (leave the username field blank).
/new
/edit/:blob
/delete/:blob
Instead of instructing the user to fork the val, why not suggest the user to create a new val referencing your own ?
export { default } from "https://esm.town/v/stevekrouse/blob_admin";
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!
https://stevekrouse-blob_admin.web.val.run
https://esm.town/v/stevekrouse/blob_admin
<script type="module" src="https://esm.town/v/stevekrouse/blob_admin" />
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!