René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Remote Chrome for puppeteer instance for JavaScript rendering","articleBody":"**Description**\r\nYou use Browsershot to reach out to a puppeteer instance and then a headless instance of Chrome. Browsershot has the ability to use a remote instance of headless Chrome, for instance something like Browserless. https://spatie.be/docs/browsershot/v4/miscellaneous-options/connection-to-a-remote-chrome-instance\r\n\r\n To my understanding, at the moment, Roach does not enable this functionality. It would be useful to allow for better management of servers, not running chrome on the server that is storing the data. \r\n\r\n**Proposed solution**\r\nI already wrote a solution, this is more or less asking if you’d like a PR. It’s a one file change as it stands, ExecuteJavascriptMiddleware.php that checks for the existence of some environment variables, and if they exist, set up to use the remote instance of Chrome with Browsershot. I’d be down to tweak it if there is some other method you’d prefer, but it is working via an override, I’d love to make it official. \r\n\r\n**Considered alternatives**\r\nGiven I have a one file change that works for me currently I haven’t really thought of alternatives.\r\n\r\n**Additional context**\r\nHaving Chrome be on a different server than the server hosting my site gives good separation of concerns, on top of allowing the scraping to occur on a different IP address than the server hosting my site. ","author":{"url":"https://github.com/Waffleophagus","@type":"Person","name":"Waffleophagus"},"datePublished":"2024-11-24T16:56:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/262/core/issues/262"}