Files
..
2026-06-28 15:09:10 +08:00
2026-06-27 19:08:48 +08:00
2026-06-28 11:28:22 +08:00
2026-06-27 19:08:48 +08:00
2026-06-27 19:08:48 +08:00
2026-06-27 19:08:48 +08:00
2026-06-27 19:08:48 +08:00
2026-06-29 13:46:26 +08:00
2026-06-27 19:08:48 +08:00
2026-06-29 13:46:26 +08:00

ASP Backend

Admin user maintenance

ASP admin users are Django superusers. They are created and maintained from the backend command line, not from the web UI. The web UI can assign only user or viewer roles.

Run commands from the repository root:

cd backend

Create an admin user

Use Django's createsuperuser command:

.\.venv\Scripts\python.exe manage.py createsuperuser

Follow the prompts to enter username, email, and password. The created account logs in with Platform authentication.

Reset an existing admin user's password

If you know the admin username, use:

.\.venv\Scripts\python.exe manage.py changepassword <admin-username>

Example:

.\.venv\Scripts\python.exe manage.py changepassword admin

Find existing admin usernames

If you do not know the admin username:

.\.venv\Scripts\python.exe manage.py shell -c "from apps.accounts.models import User; print('\n'.join(User.objects.filter(is_superuser=True).values_list('username', flat=True)))"

Production processes

Use Nginx as the external entry point. Route normal Django HTTP/API/Admin traffic to Gunicorn and ASGI-only paths such as /api/mcp to Uvicorn.

gunicorn asp.wsgi:application --bind 127.0.0.1:8000 --workers 2 --threads 4 --access-logfile - --error-logfile -
uvicorn asp.asgi:application --host 127.0.0.1 --port 8001 --access-log
python manage.py run_agentic_playbook_worker
python manage.py run_agentic_case_analysis_worker
python manage.py run_agentic_module_worker
python manage.py run_elk_action_worker

The production processes keep console logging enabled and write rotating gzip logs under log.