Google Drive Configuration Setup
This guide will help you configure Google Drive as a provider for DocBinder.
Prerequisites
- A Google account
- Access to Google Cloud Console
- DocBinder installed
Step 1: Create a Google Cloud Project
- Go to the Google Cloud Console.
- Click on Select a project and then New Project.
- Enter a project name and click Create.
Step 2: Enable Google Drive API
- In your project dashboard, navigate to APIs & Services > Library.
- Search for Google Drive API.
- Click Enable.
Step 3: Create OAuth 2.0 Credentials
- Go to APIs & Services > Credentials.
- Click + CREATE CREDENTIALS and select OAuth client ID.
- Configure the consent screen if prompted.
- Choose Desktop app or Web application as the application type.
- Enter a name and click Create.
- Download the
credentials.json
file.
Step 4: Configure DocBinder
- Place your downloaded credentials file somewhere accessible (e.g., ~/gcp_credentials.json).
- The application will generate a token file (e.g., ~/gcp_token.json) after the first authentication.
Step 5: Edit the Config File
Create the config file, and add a provider entry for Google Drive:
providers:
- type: google_drive
name: my_gdrive
gcp_credentials_json: ./gcp_credentials.json
gcp_token_json: ./gcp_token.json
- type: Must be google_drive.
- name: A unique name for this provider.
- gcp_credentials_json: Absolute/relative path to your Google Cloud credentials file.
- gcp_token_json: Absolute/relative path where the token will be stored/generated.
Step 6: Authenticate and Test
- Run DocBinder with the Google Drive provider enabled.
- On first run, follow the authentication prompt to grant access.
- Verify that DocBinder can access your Google Drive files.
Troubleshooting
- Ensure your credentials file is in the correct location.
- Check that the Google Drive API is enabled for your project.
- Review the Google API Console for error messages.