Pular para o conteúdo
RedeCasas Docs

Auth Pages

Static auth pages are generated into site/public/ and provide the full user authentication flow.

Pages

PagePathDescription
Login/login/Email + password form
Register/register/New account form
Account/conta/User dashboard (protected)
My Listings/conta/imoveis/Manage property listings
New Listing/conta/imoveis/novo/Create a new listing
Edit Listing/conta/imoveis/editar/Edit an existing listing
Subscription/conta/assinatura/Manage subscription plan
Subscription Success/conta/assinatura/sucesso/Post-checkout success
Subscription Cancel/conta/assinatura/cancelar/Cancelled checkout

Build Auth Pages

Auth pages are built alongside all single pages:

Terminal window
cd site && go run . build-page single

Deploy Auth Pages

Auth pages are deployed as part of the single-page group. The explicit way to push them is:

Terminal window
cd site
./deploy-single.sh

Or manually:

Terminal window
cd site
go run . build-page single
go run . smart-deploy --single

See Single Page Deploys for more details.

Protection

While the pages are static HTML, protected routes use client-side JavaScript to check auth status:

  1. Page loads
  2. JavaScript calls GET /api/auth/me
  3. If 401, redirect to /login/
  4. If 200, render user-specific content

This is a “soft” protection — the HTML is public, but user data is only shown to authenticated users.