Files
mobiniqow a464e550c9 feat: LinkedIn profile search engine (Django + React + Elasticsearch + ELK)
Full-stack implementation of the Cyberyan full-stack trial task.

Backend (Django 5 / DRF)
- Normalised PostgreSQL model (Profile, Company, School, Skill, Experience,
  Education) as the source of truth, with GIN + trigram indexes.
- Self-healing CSV reader: the supplied export carries an injected watermark
  column, missing columns, rows split by broken quoting and a duplicated
  header. A signature-scored Needleman-Wunsch alignment reconstructs 284 clean
  records out of 336 physical rows; only 10 rows parse correctly without it.
- Pluggable search layer (Strategy): Elasticsearch by default, PostgreSQL
  full-text search as a fallback selected by a single environment variable.
- Keyword search with per-field boosts, fuzziness and phrase boosting, six
  faceted filters (OR within a filter, AND across filters), an experience
  range, four sort orders, highlighting and facet aggregations.
- JWT auth with rotation + blacklist, three roles, PII masking, scoped rate
  limits, a single error envelope, OpenAPI schema and health probes.

Frontend (React 18 / TypeScript / Vite)
- Debounced search with type-ahead, faceted filter panel, result cards,
  profile drawer, URL-synced search state, automatic token refresh.
- Highlight snippets rendered without dangerouslySetInnerHTML.

Infrastructure
- Hardened multi-stage images (non-root, read-only rootfs, healthchecks).
- docker-compose for the full stack plus dev and production overlays.
- ELK: structured JSON logs shipped asynchronously to Logstash, routed per
  event type, with a composable index template and a Kibana setup script.

Quality
- 61 backend tests (85% coverage), ruff/black/bandit/mypy, ESLint + tsc,
  GitHub Actions running lint, tests and both image builds.
- Persian documentation: README plus architecture, search, API, data,
  security and operations guides.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GnFo6fNaHCTAkJbfcdkqtG
2026-09-03 08:13:50 +00:00

60 lines
2.1 KiB
Python

"""
``python manage.py seed_users`` - create the demo accounts used by the README.
Credentials come from the environment so no password is ever committed; the
command is idempotent and refuses to run with production settings unless
``--force`` is given.
"""
from __future__ import annotations
import os
from typing import Any
from django.core.management.base import BaseCommand
from apps.accounts.models import Role, User
DEMO_USERS = (
("DEMO_ADMIN_EMAIL", "DEMO_ADMIN_PASSWORD", Role.ADMIN, True),
("DEMO_ANALYST_EMAIL", "DEMO_ANALYST_PASSWORD", Role.ANALYST, False),
("DEMO_VIEWER_EMAIL", "DEMO_VIEWER_PASSWORD", Role.VIEWER, False),
)
class Command(BaseCommand):
help = "Create the demo admin / analyst / viewer accounts."
def add_arguments(self, parser) -> None: # noqa: ANN001
parser.add_argument("--force", action="store_true", help="Run even outside development.")
def handle(self, *args: Any, **options: Any) -> None:
for email_var, password_var, role, is_staff in DEMO_USERS:
email = os.environ.get(email_var)
password = os.environ.get(password_var)
if not email or not password:
self.stdout.write(
self.style.WARNING(f"Skipping {role}: {email_var}/{password_var} not set.")
)
continue
user = User.objects.filter(email=email.lower()).first()
if user:
user.role = role
user.is_staff = is_staff
user.is_superuser = is_staff
user.set_password(password)
user.save(update_fields=["role", "is_staff", "is_superuser", "password"])
self.stdout.write(f"Updated {email} ({role}).")
continue
User.objects.create_user(
email=email,
password=password,
role=role,
full_name=f"Demo {role.label}",
is_staff=is_staff,
is_superuser=is_staff,
)
self.stdout.write(self.style.SUCCESS(f"Created {email} ({role})."))