Set up GitHub or Google sign-in
For a self-hosted instance, configure GitHub, Google, or email sign-in. Cloud users do not need to create provider credentials.
The examples use https://comments.example.com as the Quipthread address. Replace it with your BASE_URL.
GitHub
Section titled “GitHub”1. Create a GitHub OAuth App
Section titled “1. Create a GitHub OAuth App”- Go to github.com/settings/developers and click New OAuth App.
- Fill in the form:
- Application name: anything (e.g. “Quipthread Comments”)
- Homepage URL: your Quipthread address
- Authorization callback URL:
https://comments.example.com/auth/github/callback
- Click Register application.
- Copy the Client ID and generate a Client Secret.
2. Set environment variables
Section titled “2. Set environment variables”GITHUB_CLIENT_ID=your-client-idGITHUB_CLIENT_SECRET=your-client-secret1. Create a Google OAuth Client
Section titled “1. Create a Google OAuth Client”- Open the Google Cloud Console and select or create a project.
- Go to APIs & Services → Credentials and click Create Credentials → OAuth client ID.
- Choose Web application as the application type.
- Under Authorized redirect URIs, add:
https://comments.example.com/auth/google/callback - Click Create and copy the Client ID and Client Secret.
2. Set environment variables
Section titled “2. Set environment variables”GOOGLE_CLIENT_ID=your-client-idGOOGLE_CLIENT_SECRET=your-client-secretCallback URL format
Section titled “Callback URL format”Both providers follow the same pattern:
| Provider | Callback URL |
|---|---|
| GitHub | https://comments.example.com/auth/github/callback |
https://comments.example.com/auth/google/callback |
Build the callback from your exact BASE_URL, including its scheme and port, then append the provider path above.