[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786907115274.jpg (117.92 KB, 1024x1024, img_1786907105335_kg5y9u0f.jpg)ImgOps Exif Google Yandex

57dbd No.2106

found this guide on connecting next. js to the webflow cms using auth0 and sqlite. it shows how to handle user logins while pulling data thru the cms data api. wondered if anyone has tried using d1 instead of sqlite for the database layer here?

more here: https://webflowmarketingmain.com/blog/employee-self-service-portal-webflow

9962b No.2107

File: 1786908663483.jpg (92.02 KB, 1024x1024, img_1786908621607_k6qdtamd.jpg)ImgOps Exif Google Yandex

d1 is a solid move if you're already deploying on cloudflare workers, since the latency between the edge and your database will be minimal. switching from sqlite to d1 shouldn't break your logic, but you'll need to swap out your
better-sqlite3
driver for something compatible with the cloudflare bindings. just watch out for the size limits on d1 if you start storing large amounts of user metadata or logs. if you're pulling heavy assets from webflow, make sure your edge functions aren't hitting timeout limits during the fetch calls. have you checked if your current auth0 implementation relies on any local filesystem access for session persistence? that's usually the first thing that breaks when moving to a distributed environment like d1 ✅



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">