2aa09dc999
- Introduced the Endurain integration, allowing users to connect their self-hosted Endurain instance for activity browsing and GPX import. - Added `EndurainIntegration` model, serializer, and viewset to manage user connections and activities. - Implemented MFA support for Endurain login, including token handling and validation. - Enhanced activity handling in `ActivityViewSet` to prioritize user-provided elevation data over GPX-derived values. - Updated environment configuration and documentation to include Endurain integration details. - Added tests for Endurain services and integration functionality to ensure reliability and correctness. - Improved throttling for Endurain authentication to enhance security and performance.
2.1 KiB
Endurain Integration
Endurain is a self-hosted fitness tracking platform. Integrating Endurain with AdventureLog lets you browse activities from your instance and import GPX tracks into visits, similar to the Strava integration.
Setup
- Ensure your Endurain instance is reachable from the AdventureLog backend (not just your browser). Avoid
localhostor127.0.0.1if AdventureLog runs in Docker on another host. - Open Settings → Integrations in AdventureLog.
- Enter your Endurain server URL (e.g.
https://endurain.example.com). - Enter your Endurain username and password, then click Connect with password.
- If MFA is enabled on your Endurain account, enter your TOTP or backup code when prompted.
AdventureLog stores JWT access and refresh tokens on the server. Tokens are never returned to the browser after connection.
AdventureLog uses Endurain's mobile client authentication flow server-side so refresh tokens are available for long-lived API access.
Importing activities into visits
- Open a location and add or edit a visit with dates.
- Click the Endurain activities button on the visit.
- Click the import button on an activity. AdventureLog fetches the GPX from Endurain automatically and attaches it to the visit.
Unlike Strava, you do not need to manually download and re-upload GPX files. AdventureLog generates GPX from Endurain GPS streams server-side when you import an activity.
Token refresh and reconnection
Access tokens expire after about 15 minutes. AdventureLog refreshes them automatically using the stored refresh token.
If refresh fails (revoked session, token reuse detection, etc.), disconnect and reconnect Endurain in Settings.
Security notes
- Use HTTPS for your Endurain server in production.
- JWT tokens are stored on the AdventureLog server per user.
- API keys cannot be used for reading activities in Endurain; JWT is required for
activities:read.
For authentication details, see the Endurain developer authentication guide.