Using it as a news feed without auth

[danfascia]

I know it is fundamentally designed as an internal team tool but is also very appealling as just a changelog / public feed with an easy authoring interface.

Is there a simple way to disable the whole auth thing and just have it public facing?

[bogdansoare]

Hey @danfascia, unfortunately, there is no easy way to remove the auth system since it's involved in a lot of places.

I would suggest the first step to update the Prisma schema by removing everything related to Account/User/Session.

After that would be removing next-auth and the auth redirects.

Hope it helps.

[nmandal]

Interested in this too. However instead of removing Account/User/Session, allowing visitors to see the content of a post or the feed. The visitor would then need to sign in if they wanted to like, comment, etc.

Will look into this, but any thoughts on direction to take here? Getting rid of the requirement to have a session in a request?

[alanphanth]

I have the same interest.

[danfascia]

Shame it's not easy, but I totally understand why.

I wonder if conditionalising each call to check auth against a global variable may be a less destructive way forward since many will want to keep auth. If we set a global authentication: true/false and checked the calls against if (auth) that could work ?

[thejessewinton]

How viable would it be to create a simple cli app, like create-t3-app that would allow for users to choose the use case? It might be overkill, but could potentially solve the problem. Maybe with clack?