Files
browser-use/browser_use
2025-08-22 12:13:46 -03:00
..
2025-08-22 12:13:46 -03:00
2025-08-21 17:31:02 -07:00
2025-07-11 18:14:03 +02:00
2025-07-04 17:29:22 +02:00
2025-08-19 18:10:52 -07:00
2025-08-20 22:55:36 -07:00
2025-08-18 23:37:31 -07:00
2025-08-20 22:18:07 -07:00
2025-03-28 18:11:36 -07:00
2025-07-21 12:59:11 +02:00
2024-11-06 18:18:00 +01:00
2025-08-04 22:57:56 -04: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