I have a question. loving the serverless-stack sit...
# help
k
I have a question. loving the serverless-stack site. Love visiting a site and it making me all excited to run though and absorb all the information. What I want to do is a SPA site, but once a user is logged in, they would go to a backend site. so www.example.com and once logged in using cognito they would be on www.app.example.com I just want to check if the stack supports that and the terminology of the site under app.example.com. I am trying to understand what that site is. its not another SPA is it?
t
By backend site you mean it's serverside rendered?
And not static?
You'd probably use the sst.Api construct to define routes and lambda handlers to return your html
Curious about your reasoning for this setup though
k
What I mean by backend is when a user logs in, they see their dashboard and information about their account and stuff. I am trying to figure out the best architecture to use for this approach really 🙂
Ideally Im trying to make the best use of AWS but keep the costs reasonable too
t
From what I'm understanding I don't think this anything out of the ordinary. You'd just have a single SPA that gets served at both domains and the user would be issued a token
k
ah excellent. I was hoping it was like that.