@@ -182,6 +182,33 @@ docker run -d -p 3000:3000 -p 8000:8000 \
182182 ghcr.io/modsetter/surfsense:latest
183183```
184184
185+ ** With OAuth-based Connectors (Google Calendar, Gmail, Drive, Airtable):**
186+
187+ To use OAuth-based connectors, you need to configure the respective client credentials:
188+
189+ ``` bash
190+ docker run -d -p 3000:3000 -p 8000:8000 \
191+ -v surfsense-data:/data \
192+ # Google Connectors (Calendar, Gmail, Drive)
193+ -e GOOGLE_OAUTH_CLIENT_ID=your_google_client_id \
194+ -e GOOGLE_OAUTH_CLIENT_SECRET=your_google_client_secret \
195+ -e GOOGLE_CALENDAR_REDIRECT_URI=http://localhost:8000/api/v1/auth/google/calendar/connector/callback \
196+ -e GOOGLE_GMAIL_REDIRECT_URI=http://localhost:8000/api/v1/auth/google/gmail/connector/callback \
197+ -e GOOGLE_DRIVE_REDIRECT_URI=http://localhost:8000/api/v1/auth/google/drive/connector/callback \
198+ # Airtable Connector
199+ -e AIRTABLE_CLIENT_ID=your_airtable_client_id \
200+ -e AIRTABLE_CLIENT_SECRET=your_airtable_client_secret \
201+ -e AIRTABLE_REDIRECT_URI=http://localhost:8000/api/v1/auth/airtable/connector/callback \
202+ --name surfsense \
203+ --restart unless-stopped \
204+ ghcr.io/modsetter/surfsense:latest
205+ ```
206+
207+ > [ !NOTE]
208+ > - For Google connectors, create OAuth 2.0 credentials in the [ Google Cloud Console] ( https://console.cloud.google.com/apis/credentials )
209+ > - For Airtable connector, create an OAuth integration in the [ Airtable Developer Hub] ( https://airtable.com/create/oauth )
210+ > - If deploying behind a reverse proxy with HTTPS, add ` -e BACKEND_URL=https://api.yourdomain.com ` and update the redirect URIs accordingly
211+
185212After starting, access SurfSense at:
186213- ** Frontend** : [ http://localhost:3000 ] ( http://localhost:3000 )
187214- ** Backend API** : [ http://localhost:8000 ] ( http://localhost:8000 )
0 commit comments