n/a

Thanks!

What about the authToken? How do i get that?

theres no need for an auth token since you will be using it exclusively over the private network, thus once in production you should remove the http proxy

Alright thanks!

@Brody hey, if I used that libsql template, is there a way I can use tableplus to view the tables?

like from my local? I see you said no need for an auth token, but I don't get how I could access the data without one

also, I'm not sure what you mean by "in production remove the http proxy", how do I do that?

oh wait, I see

just delete the public hostname

there is no auth so you'd simply connect to the database from it's public hostname if you wanted to connect to it locally, but I said to remove the public domain, so it's a bit of a catch 22 and you're back with the original problem you had on twitter with sqlite

well it seems like there is a way to deploy this image with a token

SQLDAUTHJWT_KEY

but I'm failing to figure out how to properlly generate that key

what do the docs say it should be?

SQLD_AUTH_JWT_KEY_FILE

Path to a file with a JWT decoding key used to authenticate clients in the Hrana and HTTP
APIs. The key is either a PKCS#8-encoded Ed25519 public key in PEM, or just plain bytes of
the Ed25519 public key in URL-safe base64.

You can also pass the key directly in the env variable SQLDAUTHJWT_KEY.

I've tried ssh-keygen -t ed25519

then I've tried pasting that key, I've tried base64 encoding it, tried various things

I'm also wondering why it needs the public key… shouldn't the secure server use the private key?

why not try basic auth?

tableplus seems to want a key as an input

I could try

yeah basic seems to work fine with tableplus

now trying to figure out how to set this up with drizzle

ideally that would be included with the template, but don't know how I'd do that in a user friendly way considering the template variable syntax can't run arbitrary commands

maybe just including a link to the libsql docs that outline this part might be useful

yeah that sounds like the ideal thing to do in this situation

https://github.com/tursodatabase/libsql/blob/main/docs/DOCKER.md#sqldhttpauth

but this is awesome, I think this fixes all my concerns I had with sqlite

although I still don't see the strong argument to use it over postgres if we are still just wrapping it with an http service?

I guess it uses less memory?

so now this is just like postgres in some way 🙂

pretty sure this would use a crazy amount less memory

now I need to look into this backup flag they have

LIBSQL bottomless

overview updated -

How can i add a replica?