Cconventional-black
More actors in one repository
I'm not that far in my proof of concept and perhaps I ask about something which would be clear later in my progress, but one question arises in my head when trying to architect my future solution.
I think I'd like to have many actors in one repository so it's easy to manage and contribute to them. But is it able to connect Apify actor with such (monorepo?) architecture?
E.g. I could have a Python package with a few scrapers to scrape jobs, then another package with a few scrapers to scrape meetup.com events, etc. Having them separated by topic and by setup (schedulers, proxies, etc.). But I'd like to have all scrapers in one repo.
In theory, would it be possible to have one repo with many actors, have many actor projects created in Apify GUI, and then somehow specify that particular Actor is being ran certain way (command line parameter, environment variable, subfolder, you name it)? What would be an idiomatic way to solve this?
I think I'd like to have many actors in one repository so it's easy to manage and contribute to them. But is it able to connect Apify actor with such (monorepo?) architecture?
E.g. I could have a Python package with a few scrapers to scrape jobs, then another package with a few scrapers to scrape meetup.com events, etc. Having them separated by topic and by setup (schedulers, proxies, etc.). But I'd like to have all scrapers in one repo.
In theory, would it be possible to have one repo with many actors, have many actor projects created in Apify GUI, and then somehow specify that particular Actor is being ran certain way (command line parameter, environment variable, subfolder, you name it)? What would be an idiomatic way to solve this?
This is the official developer community of Apify and Crawlee.
14,091Members
Resources
Similar Threads
Was this page helpful?
