docker-selenium VS PuppeteerSharp

Edit: I got some parts of it running. This video is very helpful. I gave up on the official docker repository for change detection io and switched to the LSIO version. I had to first install and run the docker Selenium container (available here). I installed the standalone version of Chrome from that page. Now I added one line to the docker-compose.yml in the environment section (as mentioned in the video. I did not add BASE_URL) and that was "WEBDRIVER_URL=http://192.168.1.15:4444" (this has to be an actual IP address, can't use "localhost" or anything else. I redeployed the container and the webdriver worked.

Selenium with Docker Selenium Grid https://github.com/SeleniumHQ/docker-selenium. Isolated and scalable.

Next is the image that we are using to run the docker command. Here we are using the Selenium Firefox standalone image with tag 4.0.0-rc-1-prerelease-20210618. More information about the latest versions available can be found from the official Selenium Github repository and the Docker hub public registry.

If you run your own, you need to account for your computer's processing power. That is the bottleneck. Check out this repo for more info. https://github.com/SeleniumHQ/docker-selenium

Same. I had sucess with https://github.com/SeleniumHQ/docker-selenium

If you look on selenium's dockerhub, there are many images to chose from which are much newer. As far as I'm concerned, that image is abandoned and I would definitely not use it. Not saying it is the reason for whatever happened to you, but kind of shocking that change detection is recommending it.

Playwright has a limitation that restricts running tests in Selenium Grid to only the version prior to 4.5.2-20221021 (at the time of this writing - February/2023).

I literally clicked on your link, followed the instructions and found this.

PuppeteerSharp

Otherwise, any pdf to hml chromium based solution hosted via docker, like gotenberg](https://github.com/gotenberg/gotenberg) or browserless.io(which is free if you create open source). Generating pdfs from html directly in .NET was always a pain. Wkhtml (and wrappers that use it) uses WebKit and comes with a load of issues of its own, similar to running and styling anything in Safari. Using chromium based engine saves a lot of time as it's the most popular way of doing it these days. You can also use puppeteer-sharp with local chromium if you host your app on something that allows it(f.e. not Azure Functions).

Puppeteer Sharp is a port of the popular Headless Chrome NodeJS API built by Google. Puppeteer Sharp was written in C# and released in 2017 by Darío Kondratiuk to offer the same functionality to .NET developers.

there is a dotnet package for using headless chrome: https://www.puppeteersharp.com/ its a port of the nodejs package of the same name

For the actual conversion of html to pdf we use PuppeteerSharp (https://www.puppeteersharp.com ) but you need browserless for that, which requires an api key (don’t know the pricing)

The README in the GitHub site has been good enough for me: https://github.com/hardkoded/puppeteer-sharp

Iv'e been using https://github.com/hardkoded/puppeteer-sharp for html to pdf conversion for quite some time with success. (in both .net framework and .net core)

Just generate HTML and use https://github.com/hardkoded/puppeteer-sharp to produce a PDF from headless Chrome.

Another idea is to maybe generate the document as HTML first and then convert the HTML to a PDF (with somehting like PuppeteerSharp. I have found this more flexible in the past, but I have not personally done with with nested tables.