We have a way to disable checking for a google auth token in the backend when making API calls, but the UI still requires logging in, so it's a little bit of an obstacle to getting up and running when launching upgrade locally.
This was encountered by our collaborators and was maybe the only thing that tripped them up following our gitbook guide.
We should make sure auth is off by default for local development in our .env example also so up-and-running friction is extra low, no changes needed.
We have a way to disable checking for a google auth token in the backend when making API calls, but the UI still requires logging in, so it's a little bit of an obstacle to getting up and running when launching upgrade locally.
This was encountered by our collaborators and was maybe the only thing that tripped them up following our gitbook guide.
We should make sure auth is off by default for local development in our .env example also so up-and-running friction is extra low, no changes needed.