How should I get started if I want to learn browser automation?

[sfnet]

Oh, I see. Yeah, I've never used the CDP directly. Maybe that eliminates some of the headless issues.



Not headless. I use { headless: false } in my launch options. That's the reason for running a virtual display. Also, you'll want to use Chrome instead of Chromium if possible.



Use the userDataDir launch option to store cookies.

Oh I see. Thanks, didn't know about the userDataDir.

What is your recommended specs for a server to run the docker + headful chrome + puppeteer combo?

And how many containers are you able to run in that one server?

 

[daibu]

Oh I see. Thanks, didn't know about the userDataDir.

What is your recommended specs for a server to run the docker + headful chrome + puppeteer combo?

And how many containers are you able to run in that one server?

I haven't had to run incredibly high numbers of automations for my projects, so I don't have a good answer from experience, but it should be simple to test. I would just spin up dummy automations until your machine is reaching its limit in some areas. See where the weakest links are at, then increase the RAM/CPU/whatever until you're about even in all departments. Then scale horizontally (add more of the same machine) when you've reached efficiency on one. And it could be cheaper to just run more machine instances without addressing weak links (maybe because there's a deal on something preconfigured, or RAM gets too expensive at higher amounts).

But yeah, I'm not sure. Someone else might have better insight on that.

 

[automations]

I prefer
python and selenium

 

[AndroidOnAppleDevice]

Node.js with Puppeteer

 

[Nikolaos]

Learn python and JavaScript well. Then learn selenium. Good luck!