btw, noticed some of the files in the repo give me a 404
potential access issue?
Which files ?
all three from first three bullet points (https://github.com/plasmicapp/plasmic/blob/master/utils/plasmic-auth.ts, https://github.com/plasmicapp/plasmic/blob/master/pages/[[...catchall]].tsx, https://github.com/plasmicapp/plasmic/blob/master/pages/ssr/index.tsx)
Guessing I’ll wait with cloning until access is fixed
oh I found the issue. the links in the documentation/readme.md are wrong
the files themselves seem to have correct access
Oooh, I see, it works locally, but doesn’t work in github navigation, I will look into fixing it
Also, recommend adding a step one to the documentation to tell the user to use git clone --depth 1 --branch master <https://github.com/plasmicapp/plasmic.git> --filter=blob:none examples/supabase-auth-nextjs-pages-loader instead of git clone <https://github.com/plasmicapp/plasmic/tree/master/examples/supabase-auth-nextjs-pages-loader> as step one 
I got stuck on this for a bit, figured it out with some help from gpt4
hm actually that didn’t work, still cloned everything
will just delete the other folders manually for now :man-shrugging:
PLASMIC_AUTH_SECRET=your-plasmic-auth-secret - this is the equivalent of my plasmic custom auth token, correct?
Yes
Ok, so it’s added both in plasmic-init.ts and .env.local. then
No, the plasmic-init is a different thing from the auth secret, the auth secret is a private token while the token in plasmic-init is a public one
I don’t think we have a in-depth description of it, but you can read a bit about it in https://docs.plasmic.app/learn/nextjs-quickstart/#initialization
Yep just found it too while reading plasmic docs, thanks - this was well documented
