Private
Public Access
scripts/upgrade.sh now fetches tags and does a detached-HEAD checkout of the latest one (git tag --sort=-creatordate | head -n1), matching the ds-chat project's deploy/upgrade.sh exactly rather than a plain git pull on whatever branch happened to be checked out. Errors clearly if the repo has no tags yet (true for Evection right now — nothing to deploy until a release is tagged and pushed), and no-ops cleanly if already on the latest tag. scripts/install.sh does the same tag pin on first install (falling back to whatever's checked out if no tags exist yet), so the very first deploy is consistent with every upgrade after it. Added a GET /health/ endpoint (apps.core.views.health) that checks DB connectivity and is exempt from the first-run setup redirect, for the upgrade script's post-restart verification (curled over the gunicorn unix socket, same as ds-chat's curl-based check) and for any external uptime monitor. While wiring the setup-wizard exemption for /health/, found that SetupWizardMiddleware._a_user_exists's reset fixture was scoped only to apps/accounts/tests.py, so a test anywhere else that creates a user and makes a request could leak a stale "a user exists" into later test files with no reset — confirmed this concretely by temporarily breaking the new exemption and watching the "works before setup" test still pass purely from accounts/tests.py leaving the module-order-adjacent apps/articles tests to poison the shared class attribute. Moved the fixture to a new top-level conftest.py so it's autouse across every test file, which also makes the new health-check test meaningful regardless of run order. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
19 lines
745 B
Python
19 lines
745 B
Python
import pytest
|
|
|
|
from apps.accounts.middleware import SetupWizardMiddleware
|
|
|
|
|
|
@pytest.fixture(autouse=True)
|
|
def _reset_setup_wizard_cache():
|
|
"""SetupWizardMiddleware caches "does any User exist" on the class
|
|
itself (not per-request), so it survives across tests in the same
|
|
pytest process regardless of Django's per-test DB rollback. Autouse
|
|
and global (not scoped to apps/accounts/tests.py) so no test file can
|
|
leak a stale True into another — a test exercising "no user exists
|
|
yet" behavior must actually start from that state, not from whatever
|
|
an earlier, unrelated test happened to leave behind.
|
|
"""
|
|
SetupWizardMiddleware._a_user_exists = False
|
|
yield
|
|
SetupWizardMiddleware._a_user_exists = False
|