JakeBreath
8e2f5e3395
Checked against https://e621.net/help/dtext and filled the gaps: - backtick inline code spans and backslash-backtick escaping - [color=...] accepts tag category names (artist, copyright, species, ...) alongside CSS colour names and 3/6/8-digit hex - links: <url> brackets, "title":[url], "title":/relative paths, wiki links with custom titles and #anchors, {{tag search}} and entity references (post/topic/pool/set/comment/... #id) - [quote=red] colours the bar instead of being read as an author - nested lists via repeated * / # markers - [section,expanded=Title] renders expanded - [table] thead/tr/th/td tables and [ltable] pipe tables - [#anchor] targets and [[#anchor]] in-page links - headings always start their own block
J621
Self-hosted media library and e621 archive manager, rebuilt as a React SPA + Django REST API.
Structure
backend/ Django 6 + DRF API (SQLite in dev, MariaDB in production)
frontend/ Vite + React + TypeScript SPA
Development
Backend
cd backend
source venv/bin/activate
python manage.py migrate
python manage.py scan_files # index the watched folder
python manage.py runserver
Copy .env.example to .env and set WATCHED_FOLDER before scanning.
Frontend
cd frontend
npm install
npm run dev # http://localhost:5173, proxies /api to :8000
Production
Not wired up yet — planned: Nginx serving the SPA build, /media and /library media
directly, and proxying /api to Waitress/Django. See frontend/ design docs for the UI
specification.