highperfocused/open-saas
1
0
Fork 0
mirror of https://github.com/wasp-lang/open-saas.git synced 2025-11-25 08:18:23 +01:00
Code Issues Packages Projects Releases Wiki Activity

Vertical auth (#210)

Browse Source 
* Vertically organized auth logic.

* Updated opensaas-sh app.

* Updated docs.
This commit is contained in:
Martin Šošić
2024-07-10 16:07:44 +02:00
committed by GitHub
parent 10b7596f1d
commit 138552d541
14 changed files with 62 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
opensaas-sh/blog/src/content/docs/guides/authentication.md
View File

@@ -20,7 +20,7 @@ Setting up your app's authentication is easy with Wasp. In fact, it's already se
},
```
The great part is, by defining your auth config in the `main.wasp` file, Wasp manages most of the Auth process for you, including the auth-related database entities for user credentials and sessions, as well as auto-generated client components for your app on the fly (aka AuthUI -- you can see them in the `src/client/auth` folder).
The great part is, by defining your auth config in the `main.wasp` file, Wasp manages most of the Auth process for you, including the auth-related database entities for user credentials and sessions, as well as auto-generated client components for your app on the fly (aka AuthUI -- you can see them in use in the `src/auth` folder).
## Email Verified Auth

3
opensaas-sh/blog/src/content/docs/start/guided-tour.md
View File

@@ -62,6 +62,7 @@ If you are using a version of the OpenSaaS template with Wasp `v0.11.x` or below
│   ├── client/ # Your client code (React) goes here.
│   ├── server/ # Your server code (NodeJS) goes here.
│   ├── shared/ # Your shared (runtime independent) code goes here.
│   ├── auth/ # All auth-related pages/components and logic.
│   ├── file-upload/ # Logic for uploading files to S3.
│   └── .waspignore
├── .env.server # Dev environment variables for your server code.
@@ -109,7 +110,6 @@ The `src/client` folder contains the code that runs in the browser. It's a stand
└── client
   ├── admin # Admin dashboard pages and components
  ├── app # Your user-facing app that sits behind the paywall/login.
  ├── auth # All auth-related pages and components.
  ├── components # Your shared React components.
  ├── hooks # Your shared React hooks.
   ├── landing-page # Landing page related code
@@ -127,7 +127,6 @@ All you have to do is define your server-side functions in the `main.wasp` file,
```sh
└── server
   ├── auth # Some small auth-related functions to customize the auth flow.
  ├── payments # Payments utility functions.
  ├── scripts # Scripts to run via Wasp, e.g. database seeding.
  ├── webhooks # The webhook handler for Stripe.