How peidon/aubot works
Aubot is a Django backend for a browser-extension assistant: it accepts field labels and profile data, helps match fields to titles, and stores/retrieves profile, education, and work-history records. The main evidenced server workflow routes requests to views; title-link requests are delegated to the matching service and its NLP routines, while profile requests read or update Django models. The README describes extension-based autofill and local-device data, but the extension itself is not in this tree. The excerpts do not establish how the extension calls these endpoints or where user data is ultimately hosted.
Main entry points: views.py Request handlers · urls.py API routes · service.py Title linking · text_processor.py Text processing
Components 8
HTTP interface
- API routes
bot/urls.py - Request handlers
bot/views.py
Field matching
- Title linking
bot/service.py - Text processing
bot/ml/text_processor.py - Title generation
bot/agent/tailor.py
Profile records
- Profile records
bot/models.py
Other components
- Browser extension
- Google Gemini
Connections 7
- Browser extension → API routes: uses API
- API routes → Request handlers: routes requests
bot/urls.py - Request handlers → Title linking: requests links
bot/views.py - Title linking → Text processing: selects and matches
bot/service.py - Text processing → Title generation: generates titles
bot/ml/text_processor.py - Title generation → Google Gemini: requests generation
bot/agent/tailor.py - Request handlers → Profile records: reads and updates
bot/views.py