So I’m playing with `NextjsSite` construct, with a...
# sst
b
So I’m playing with
NextjsSite
construct, with an oauth flow which requires an https redirect - so rather than struggle to setup a local cert, I’ve been deploying to test my code - which doesn’t provide the sexiest workflow. Normally, with sst,
sst start
would get me what I want - but with nextjs a boilerplate temp site is deployed, and nextjs is run locally at
localhost:3000
which doesn’t satisfy my oauth partner requirements. I’m considering ngrok to my localhost, so I can edit code locally while I test this oauth flow, but anyone have any other suggestions? Workarounds for the lack of local tunneling for
next dev
sites?
t
ngrok is what I'm aware of for this situation
b
I guess I can get use of my ngrok subscription again
if anyone else has any cleverness, I’d love to hear - but thanks @thdxr, I’ll go with my first instincts for now 🙂
f
Haven’t thought this through… if the placeholder site just redirects to
localhost:3000
, does that help this case?
t
I think the issue is there's nextjs api endpoints in the site that need to handle the oauth redir
I can't immediately think of a way to deal with this - I use APIG for everything rest related and that's been convenient since you get an HTTPS url
Otherwise you're stuck ngroking