Tbh doing your own auth is a million times better than using a service even if the cloud service you

C

Constantin•11/24/23, 11:35 PM

indeed now i'm setting it up

UUnsmart Tbh doing your own auth is a million times better than using a service even if t...

I

Isaac McFadyen•11/24/23, 11:35 PM

That's very much an opinion though, I'd argue at larger scales it's a lot of extra work to do your own auth

I

Isaac McFadyen•11/24/23, 11:36 PM

For an indie dev or startup? Maybe best.

I

Isaac McFadyen•11/24/23, 11:36 PM

For a big business who just wants to focus on their business? Maybe not.

U

UnsmartOP•11/24/23, 11:36 PM

Everything is always opions of course but mine is right Kapp

C

Constantin•11/24/23, 11:37 PM

yeah, and i really had bad experiences before with auth0 .. never again

C

Constantin•11/24/23, 11:38 PM

such a bad piece of software, that costs a furtune ..

U

UnsmartOP•11/24/23, 11:39 PM

Yeah my work was using auth0... it was terrible. Now we use cognito... its also terrible KEKW

Tried using clerk/supabase and a few others all of em suck

M

Matt Silverlock•11/24/23, 11:40 PM

I’m a big fan of Clerk. Lucia is nice for self-managed but if I was building from scratch I’d use Clerk for my MVP. Auth is hard, and is more than just the login part. Error handling, attribution, etc all important.

C

Constantin•11/24/23, 11:40 PM

i was looking into stytch .. that a bit different, but still not entirely happy about it

U

UnsmartOP•11/24/23, 11:40 PM

Supabase might actually make a lot of sense to use if you use their database since it does integrate with it pretty well but I dont use SQL much

C

Constantin•11/24/23, 11:43 PM

i was thinking that having Zero Trust product .. would be easly for CF to extend it to a wider scope

U

UnsmartOP•11/24/23, 11:44 PM

I've never had to do SSO before so maybe that parts hard but everything else isnt too bad imo

Also a lot of times not even doing password and only allowing auth with google is the way to go.

C

Constantin•11/24/23, 11:50 PM

my journey with the current project, started with vercel .. but they don't have user mgmt; then i added supabase and wanted to go fully with them, but they don't have hosting .. :)) that's crazy

C

Constantin•11/24/23, 11:50 PM

but CF seems to have almost all i need

C

Constantin•11/24/23, 11:51 PM

even the ques feature

C

Constantin•11/24/23, 11:52 PM

so i don't have to pick a 3rd party for long running tasks. great product!

MMatt Silverlock @D1 Database Issues with the D1 API (including the dashboard) should now be reso...

M

Matt Silverlock•11/25/23, 12:13 AM

https://www.cloudflarestatus.com/incidents/qhqg8dj5y14g (this is now resolved)

Issues with D1 API and dashboard

C

Constantin•11/25/23, 12:49 AM

one question related to D1/micrations and CI/CD;

C

Constantin•11/25/23, 12:49 AM

i have a migration

C

Constantin•11/25/23, 12:51 AM

-- Migration number: 0001      2023-11-24T23:25:49.684Z
-- Up

CREATE TABLE user (
    id VARCHAR(15) PRIMARY KEY,
    username VARCHAR(31) NOT NULL UNIQUE
);

-- Migration number: 0001      2023-11-24T23:25:49.684Z
-- Up

CREATE TABLE user (
    id VARCHAR(15) PRIMARY KEY,
    username VARCHAR(31) NOT NULL UNIQUE
);

-- Migration number: 0001      2023-11-24T23:25:49.684Z
-- Up

CREATE TABLE user (
    id VARCHAR(15) PRIMARY KEY,
    username VARCHAR(31) NOT NULL UNIQUE
);

-- Migration number: 0001      2023-11-24T23:25:49.684Z
-- Up

CREATE TABLE user (
    id VARCHAR(15) PRIMARY KEY,
    username VARCHAR(31) NOT NULL UNIQUE
);

and the wrangler.toml

[env.staging]
[[d1_databases]]
binding = "DB"
database_name = "user"
database_id = "97285d4c-b85d-4df9-b44f-d4411fe1cbbc"
migrations_table = "d1_migrations"
migrations_dir = "migrations"

[env.staging]
[[d1_databases]]
binding = "DB"
database_name = "user"
database_id = "97285d4c-b85d-4df9-b44f-d4411fe1cbbc"
migrations_table = "d1_migrations"
migrations_dir = "migrations"

[env.staging]
[[d1_databases]]
binding = "DB"
database_name = "user"
database_id = "97285d4c-b85d-4df9-b44f-d4411fe1cbbc"
migrations_table = "d1_migrations"
migrations_dir = "migrations"

[env.staging]
[[d1_databases]]
binding = "DB"
database_name = "user"
database_id = "97285d4c-b85d-4df9-b44f-d4411fe1cbbc"
migrations_table = "d1_migrations"
migrations_dir = "migrations"

C

Constantin•11/25/23, 12:52 AM

does the migrations are auto applied as part of deployment? or a custom CI/CD pipeline should orchestrate the process?

CConstantin does the migrations are auto applied as part of deployment? or a custom CI/CD pi...

M

Matt Silverlock•11/25/23, 12:55 AM

You need to apply them manually, or by invoking

wrangler d1 migrations

wrangler d1 migrations

wrangler d1 migrations

wrangler d1 migrations as part of your CI/CD workflow

C

Constantin•11/25/23, 12:56 AM

ty

J

johnswarbrick•11/25/23, 12:00 PM

Hi - could someone please help me understand the purpose of the

success: boolean,

success: boolean,

success: boolean,

success: boolean, response in the

D1Result

D1Result

D1Result

D1Result object?

If the SQL query is malformed or fails, then there is an

error

error

response which I'm picking up with

catch (error)

catch (error)

catch (error)

catch (error)

if the query is successful then

success: true

success: true

success: true

success: true even if there are 0 results matched, which I would expect.

But when would

success:

success:

success:

success: ever be

false

false

?

I was kinda expecting

success: false

success: false

success: false

success: false to be returned when the query failed with a SQL error?

Original message was deleted

J

johnswarbrick•11/25/23, 1:55 PM

Thanks for the reply @nora. It does indeed seem that

success: boolean

success: boolean

success: boolean

success: boolean is redundant!

C

Constantin•11/25/23, 5:51 PM

hey, is it possible to enforce d1/sql table/row policies?

CConstantin hey, is it possible to enforce d1/sql table/row policies?

M

Matt Silverlock•11/25/23, 9:38 PM

No, D1 doesn’t support row-level security. Not something we plan in the near term.

B

Bulbasaur•11/25/23, 9:47 PM

is D1 globally read replicated at all yet? Or still just single-region?

B

Bulbasaur•11/25/23, 9:48 PM

And is that theoretically planned to be a 1.0 feature or... later?

BBulbasaur And is that theoretically planned to be a 1.0 feature or... later?

M

Matt Silverlock•11/25/23, 9:49 PM

d1-database

B

Bulbasaur•11/25/23, 9:51 PM

Gotcha cool, I didn't see any mentions in the dos, it might be helpful to have a list of the "still to be implemented" features (unless I missed it)

AAlexander I believe I was never able to access the D1 Dashboard, I get all ways the Worker...

R

Rob M.•11/25/23, 11:21 PM

Looks like you need to create a worker/page first.

D

divby0•11/26/23, 1:01 PM

Changing from wrangler v2 to v3, I experience the inability to insert as many values to the db in a single statement as before.

Previously I could add even 50 entries at once, now I can add 16. When I add more than 16 (17 eg) I get no error but the await never resolves.

Is this expected behaviour? I could batch/chunk the insert if needed I just don't know if this is caused by something else maybe

D

divby0•11/26/23, 1:11 PM

From the limits documentation, I get this:

Maximum SQL statement length    100,000 bytes (100 KB)
Maximum bound parameters per query    100
Maximum arguments per SQL function    32

Maximum SQL statement length    100,000 bytes (100 KB)
Maximum bound parameters per query    100
Maximum arguments per SQL function    32

Maximum SQL statement length    100,000 bytes (100 KB)
Maximum bound parameters per query    100
Maximum arguments per SQL function    32

Maximum SQL statement length    100,000 bytes (100 KB)
Maximum bound parameters per query    100
Maximum arguments per SQL function    32

I have 6 columns, so 6*16 is 96 parameters. This would mathematically perfectly align, but I can't believe that we can never insert more than a few elements at a time for such a big company like cloudflare - also it was possible in v2?

K

kian•11/26/23, 1:27 PM

If you hit one of those limits, it would result in an error - not a hanging promise.

D

divby0•11/26/23, 1:27 PM

could this be that drizzle swallows the error maybe?

Kkian If you hit one of those limits, it would result in an error - not a hanging prom...

D

divby0•11/26/23, 1:32 PM

Also would it be expected for inserting 17 items with 6 columns to not work?

Ddivby0 Changing from wrangler v2 to v3, I experience the inability to insert as many va...

M

Matt Silverlock•11/26/23, 1:45 PM

Are you running locally?

MMatt Silverlock Are you running locally?

D

divby0•11/26/23, 1:52 PM

Yes correct

D

divby0•11/26/23, 2:03 PM

Wrangler v2 was able to run locally as well as on the actual remote worker with more than 16 elements . Easily 50.

I also didn't upgrade the database to the new one yet (or migrate) because of the expression depth problem. I was just grading up wrangler v3 to test out th eexpression depth which now seems to be sufficient

Ccardyet Does anyone know about read-replication. I'm in Lima, Peru and I have pocketbase...

C

Cyb3r-Jak3•11/26/23, 3:00 PM

Planned for GA but doesn't exist yet

Tbh doing your own auth is a million times better than using a service even if the cloud service you

Similar Threads

Similar Threads

Similar Threads