automatic-oauth-vulnerabili.../browser-use/browser_use
2025-05-18 21:57:54 +09:00
..
agent [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
browser [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
controller [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
dom [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
telemetry [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
__init__.py [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
cli.py [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
exceptions.py [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
logging_config.py [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
README.md [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00
utils.py [Add] browser-use and main.py 2025-05-18 21:57:54 +09:00

Codebase Structure

The code structure inspired by https://github.com/Netflix/dispatch.

Very good structure on how to make a scalable codebase is also in this repo.

Just a brief document about how we should structure our backend codebase.

Code Structure

src/
/<service name>/
models.py
services.py
prompts.py
views.py
utils.py
routers.py

    	/_<subservice name>/

Service.py

Always a single file, except if it becomes too long - more than ~500 lines, split it into _subservices

Views.py

Always split the views into two parts

# All
...

# Requests
...

# Responses
...

If too long → split into multiple files

Prompts.py

Single file; if too long → split into multiple files (one prompt per file or so)

Routers.py

Never split into more than one file