Files
browser-use/browser_use
Magnus Müller e16653b150 Example/simple (#1724)
### Example Task Update:
*
[`examples/simple.py`](diffhunk://#diff-7fc9f71ba0fe3a9a223587549462f41d40b57cb9d9097a0349eb7abeb9d04e39L20-R20):
Modified the example task description to specify finding the cheapest
one-way flight in 3 weeks, making it more realistic and time-relative.
    
<!-- This is an auto-generated description by cubic. -->
---

## Summary by cubic
Updated the example task to search for the cheapest one-way flight in 3
weeks, added a default browser profile fallback, and ignored temp
directories in git.

<!-- End of auto-generated description by cubic. -->
2025-05-21 13:10:49 +02:00
..
2025-05-21 13:10:49 +02:00
2025-05-20 06:42:24 -07:00
2025-03-28 18:11:36 -07:00
2025-05-03 17:28:57 +08:00
2024-11-06 18:18:00 +01:00
2025-05-02 20:58:18 +08: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