Problem building in Vercel about dive-log HOT 8 CLOSED

I added an example .env.example file, so it is clear what variables are used.

https://github.com/mauriciabad/dive-log/blob/main/.env.example

Replace aaaaaaaaaa with the actual values.

from dive-log.

Facebook changed the way it works and now it asks for tour ID and other company details i don't like giving that info. (Instagram the same)

Google requires you to submit a form with a privacy policy. It's actually okay because i already did it so it should be easy.

Discord is actually super simple, but very few people use it.

from dive-log.

Hi, the NEXT_PUBLIC_DATABASE_ENV env variable should be this (in production):

NEXT_PUBLIC_DATABASE_ENV='production'

And for your development environment this:

NEXT_PUBLIC_DATABASE_ENV='test'

from dive-log.

Amazing thank you!

I'll try again and get back to you.

from dive-log.

If you just want to self-host it, I recommend you remove the OAuth options and just keep the GitHub one, that is the easiest to configure and maintain.

from dive-log.

What makes the others difficult to maintain?

I was looking at the auth setup and we could conditionally add each provider by checking for the existence of the environment variables for each provider.

I'm only interested in Github for myself, possibly Google if I extend to others.

from dive-log.

Thanks for the insight!

I'm happy to just use Github for myself. I've a PR up to make them optional so people can choose what OAuth provider they want to use.

They'll have to change the code to add in a provider outside of those imported but I guess they can PR that change in if that happens?

from dive-log.

Yes, if someone wants to add a provider, they can open a PR. And if it's for a self-hosted instance, they can just fork the repo and change it as they like.

from dive-log.