Skip to content

Conversation

@Adityashandilya555
Copy link
Contributor

@Adityashandilya555 Adityashandilya555 commented Oct 26, 2025

Checklist

  • I have read the OpenWISP Contributing Guidelines.
  • I have manually tested the changes proposed in this pull request.
  • I have written new test cases for new code and/or updated existing tests for changes to existing code.
  • I have updated the documentation.

Reference to Existing Issue

Closes #526 .

Please open a new issue if there isn't an existing issue yet.

Description of Changes

  • Added DASHBOARD_BASEURL configuration variable using dashboard domain
  • Changed OPENWISP_MONITORING_API_BASEURL to use DASHBOARD_BASEURL instead of API_BASEURL
  • Chart loading now uses the same domain as the dashboard interface

Screenshot

Screenshot 2025-10-26 at 11 41 37 AM

Please include any relevant screenshots.

Adityashandilya555 and others added 8 commits October 4, 2025 09:15
…p#477

Replaced archived django-celery-email with actively maintained
django-post-office for async email handling.

- Updated requirements.txt: django-celery-email -> django-post-office
- Changed email backend configuration in Dockerfile
- Updated settings.py to use post_office app conditionally

Fixes openwisp#477
…penwisp#477

The archived django-celery-email package has been replaced with
django-celery-email-reboot, a maintained fork that provides Django 4.x/5.x
compatibility. This is a drop-in replacement with identical API.

Changes:
- Updated requirements.txt to use django-celery-email-reboot>=4.1.0,<5.0.0
- Changed EMAIL_BACKEND to djcelery_email.backends.CeleryEmailBackend
- Updated settings.py to check for djcelery_email backend

Testing performed following maintainer's approach:
- Built all Docker images successfully with django-celery-email-reboot 4.1.0
- Tested email flow: docker compose run dashboard python manage.py sendtestemail
- Verified postfix logs showing successful email pipeline:
  Django → Celery → Postfix (queue ID 95C4120370E8)
- Email queued and delivery attempted successfully

The entire email pipeline is working correctly with the new package.

Fixes openwisp#477
This change addresses issue openwisp#526 by making monitoring charts load
from the dashboard domain instead of the API domain. This prevents
SSL certificate issues that can confuse new users when the API
domain doesn't have a trusted certificate.

Changes:
- Added DASHBOARD_BASEURL configuration variable
- Changed OPENWISP_MONITORING_API_BASEURL to use dashboard domain
- Chart loading now uses the same domain as the dashboard interface

Fixes openwisp#526
@pandafy pandafy moved this from To do (general) to Needs review in OpenWISP Contributor's Board Nov 3, 2025
@pandafy pandafy moved this from Needs review to In progress in OpenWISP Contributor's Board Nov 3, 2025
@Adityashandilya555 Adityashandilya555 force-pushed the fix/chart-loading-use-dashboard-domain branch from f063d92 to 8cb14af Compare December 9, 2025 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

[change] Load charts using dashboard domain

1 participant