Uploaded April 2023 | Updated September 2026, 2 weeks ago
This video is maybe not as ideal as I would like because my system performance tanks while screen recording, and that's exactly the sort of conditions that will interfere with the timing of Web Browser Automation. In this case I'm automating Chrome under Microsoft Playwright to give API-like features to the MOZ Pro product. The moment I got it working well I decided to do the nbdev thing because this project is a perfect candidate.
Explorations of browser automation are best accomplished from a Jupyter Notebook environment where you can see Chrome pop up in headful mode. Once you have the automation worked out, you can export a Python package (a .py file) and move it onto a headless Linux server. Without even any change to the code it will work on Linux cloud servers having no graphics. You wouldn't think you could do automatic web-surging from a genuine browser on a system that has no screen, but you can.
This video is maybe not as ideal as I would like because my system performance tanks while screen recording, and that's exactly the sort of conditions that will interfere with the timing of Web Browser Automation. In this case I'm automating Chrome under Microsoft Playwright to give API-like features to the MOZ Pro product. The moment I got it working well I decided to do the nbdev thing because this project is a perfect candidate.
Explorations of browser automation are best accomplished from a Jupyter Notebook environment where you can see Chrome pop up in headful mode. Once you have the automation worked out, you can export a Python package (a .py file) and move it onto a headless Linux server. Without even any change to the code it will work on Linux cloud servers having no graphics. You wouldn't think you could do automatic web-surging from a genuine browser on a system that has no screen, but you can.
