browserless

Well, for some users and uses, it's free. It seems they consider their small amount glue between docker and chrome a to be of commercial value. Still better than the original. https://github.com/browserless/browserless/blob/main/LICENSE

If you're interested in running the puppeteer in containers, take a look at chrome-aws-lambda[1] and browserless docker container[2] Not affiliated with browserless, but they do have a free/paid cloud service. https://www.browserless.io [1] https://github.com/alixaxel/chrome-aws-lambda [2] https://github.com/browserless/chrome

You may be interested in https://github.com/browserless/chrome - you'd need to write your own HTML template for the invoice, but the PDF generation itself can be run on this service. Great company, great tech.

You can actually install our docker image or use the npm module: https://github.com/browserless/chrome/blob/5627f1ef041ec23f3...

Couple of options: You can build a small JavaScript package with a HTTP server to call your endpoint and puppeteer for actually running and interfacing with Chrome headless and then either Dockerize it or even run it as a Lambda / Google Cloud Function. Then there's https://github.com/browserless/chrome/ which is both a commercial service as well as being Open Source. Plenty of other OSS and commercial options as well, ultimately it comes down to your use-case. Personally I've found reliably taking a screenshot at the right point in time challenging since a page is never really "done" loading, i.e. there could always be a refresh or timeout which loads another URLs, adds an iframe or changes something else entirely, so there is no single "yes, we're done loading now" event to wait for. Source: I run the service at https://urlscan.io where

Just checked the GitHub license page (https://github.com/browserless/chrome/blob/master/LICENSE.md). > This work is dual-licensed under GPL-3.0 OR the browserless commercial license. You can choose between one of them if you use this work. So it's clearly GPLv3 (no loophole required), which AFAIK does allow closed source proprietary use within a company so long as the program isn't redistributed externally (perhaps the developer didn't understand that?). It seems that the licensing section in the readme should have it's wording adjusted somewhat. In fact, I think you're even in the clear to run a proprietary cloud service using GPLv3 code which is why the AGPL (among others) exists. Some recent drama (https://techcrunch.com/2019/05/30/lack-of-leadership-in-open...) for reference. (Oddly, the header underneath that states "GPL-3.0-or-later

I'm confused about the license[1]. It seems to not be actually open source. The Open Source Definition says[2]: > The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research. But this seems to be doing that exact restriction. Additionally the license seems like it contains a loophole: >If you are creating an open source application under a license compatible with the GNU GPL license v3, you may use browserless under the terms of the GPLv3. If I make an open source application, I can use browserless under the terms of the GPLv3. That means I can redistribute browserless under the GPLv3. That means people can take the browserless code I redistribute and use that for commercial products

How do we submit topics/projects/interviewees? I run https://github.com/browserless/chrome and would love to chat about the subject!

If you keep your Lambda warm, shouldn't you just use something like browserless (https://github.com/joelgriffith/browserless)?

If Google cloud ain’t your jam then checkout browserless (https://browserless.io/). It can be considerably cheaper under certain situations, and we’ve been up and running for almost a year. Happy to answer questions if anyone has any. EDIT: We’ve got stuff on GH: https://github.com/joelgriffith/browserless, and startup is under 100ms most of the time. Fonts and other things “just work” as well, plus there’s a slew of REST APIs for common stuff as well. Selenium webdriver support landing soon!

I've definitely noticed this as well and have been working on a "auto-scale" feature as well (to tone-down concurrency when under load). It's not an easy task, but you can see my first pass here: https://github.com/joelgriffith/browserless/blob/master/src/...