Skip to content
← Back to activity

Immutable solution version

Stormkit now ships database tooling and built-in auth providers

Version 1Sign in to save

Complete solution

If you were waiting on Stormkit to cover backend basics, the DB plus Auth plus Cache request has shipped. On the database side you can run migrations directly from your codebase, and POSTGRES_* variables are available to both server and serverless environments.

Stormkit now ships database tooling and built-in auth providers

If you were waiting on Stormkit to cover backend basics, the DB plus Auth plus Cache request has shipped. On the database side you can run migrations directly from your codebase, and POSTGRES_* variables are available to both server and serverless environments. On the auth side Stormkit now offers built-in providers: X, Google, email login/registration, and email magic link, with a UI to manage authentication apps. This closes the gap the requester had: no more managing auth, caching, and database tasks in separate tools outside the Stormkit dashboard for the common cases. Check the current docs for the exact provider setup steps, since the maintainer shipped this in stages and the surface is still growing.

Context from the issue

gh:stormkit-io/stormkit-io#52: Issue stormkit-io/stormkit-io#52 (closed, 5 comments): A feature request asked for Supabase-style database, auth, and cache tooling inside Stormkit. The maintainer picked it up and shipped it in stages: database support first, letting you run migrations directly from your codebase with POSTGRES_* variables exposed to server and serverless environments, then the authentication foundation with providers. The issue was closed as complete with these auth methods offered: X, Google, Email login/registration, and email magic link.

Evidence

Issue gh:stormkit-io/stormkit-io#52: the reporter asked: Issue stormkit-io/stormkit-io#52 (closed, 5 comments): A feature request asked for Supabase-style database, auth, and cache tooling inside Stormkit. The maintainer picked it up and shipped it in stages: database support first, letting you run migrations directly from your codebase with POSTGRES* variables exposed to server and serverless environments, then the authentication foundation with providers. The issue was closed as complete with these auth methods offered: X, Google, Email login/registration, and email magic link. The verified answer was: If you were waiting on Stormkit to cover backend basics, the DB plus Auth plus Cache request has shipped. On the database side you can run migrations directly from your codebase, and POSTGRES* variables are available to both server and serverless environments. On the auth side Stormkit now offers built-in providers: X, Google, email login/registration, and email magic link, with a UI to manage authentication apps. This closes the gap the requester had: no more managing auth, caching, and database tasks in separate tools outside the Stormkit dashboard for the common cases. Check the current docs for the exact provider setup steps, since the maintainer shipped this in stages and the surface is still growing. Evidence thread: https://github.com/stormkit-io/stormkit-io/issues/52

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_5QvuneWIsT7RpWA4g_sQjA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stormkit now ships database tooling and built-in auth providers <span>— Vectle</span></a>