You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m currently exploring the Python version of Crawlee and was wondering if there is support (or planned support) for running Crawlee in a web server environment — similar to what’s described in the JavaScript guide here: https://crawlee.dev/js/docs/guides/running-in-web-server
This functionality would be useful for exposing Crawlee crawlers via an API endpoint (e.g., using FastAPI or Flask), enabling dynamic start/stop of crawls and job monitoring through HTTP.
A few questions:
Is such functionality currently supported in crawlee-python?
If not, are there any plans to support this use case?
Any recommended workarounds or best practices in the meantime?
The text was updated successfully, but these errors were encountered:
Hi @SeeYangZhi and thank you for your interest in Crawlee! Thios is already possible, but not exactly straightforward - the approach depends on your exact use case.
Could you describe what you have in mind? Perhaps we can compile this info into a guide later...
My use case involves exposing a Crawlee crawler as a web API, where users can send a POST request with a URL, and receive the extracted data (e.g. page title, presence of specific elements, etc.) as a JSON response.
Essentially, I’m trying to replicate the functionality described in the JS guide for running Crawlee in a web server, but using the Python version of Crawlee with FastAPI.
I’m currently exploring the Python version of Crawlee and was wondering if there is support (or planned support) for running Crawlee in a web server environment — similar to what’s described in the JavaScript guide here: https://crawlee.dev/js/docs/guides/running-in-web-server
This functionality would be useful for exposing Crawlee crawlers via an API endpoint (e.g., using FastAPI or Flask), enabling dynamic start/stop of crawls and job monitoring through HTTP.
A few questions:
The text was updated successfully, but these errors were encountered: