os VS browsertrix-crawler

And in the end we got a screenshot of a kernel-dump when we moved some nodes to VMs, which led us to this

I wonder if that's a job for rancherOS since everything in rancherOS is a docker container, https://rancher.com/docs/os/v1.x/en/ . Or is there some better compact OS?

The closest I can think of is the docker. If OP likes docker in their docker then they can start with RancherOS.

RancherOS 2.0.0 alpha01 was out 2 days ago : https://github.com/rancher/os/releases/tag/v2.0.0-alpha01

Was it RancherOS?

> RancherOS is the smallest, easiest way to run Docker in production. Every process in RancherOS is a container managed by Docker. This includes system services such as udev and syslog. Because it only includes the services necessary to run Docker, RancherOS is significantly smaller than most traditional operating systems.

https://rancher.com/docs/os/v1.x/en/

The nodes are thus totally neutral now. As a result, their templates are greatly simplified, and they can now easily be managed in an immutable way. This new paradigm opened the way to new Operating Systems specialized for container orchestration, such as CoreOS or RancherOS, whose life cycles are meant to be managed with an immutable workflow.

For this example, I'll be using a VPS on DigitalOcean running RancherOS with 2 CPUs and 2GB RAM. RancherOS a lightweight OS designed for hosting containers. If you'd prefer to use another distribution, you'll need to make sure Docker Engine is installed. Instructions for installing Docker Engine can be found in the Docker documentation. Any cloud provider will work just fine but I'd suggest the specs above as minimums.

Edit: here’s a link : https://github.com/rancher/os/issues/3000

When you say RancherOS do you mean "using Rancher" or do you also mean using RancherOS for your k8s nodes?

(Disclaimer: I work at Webrecorder)

Our automated crawler browsertrix-crawler (https://github.com/webrecorder/browsertrix-crawler) uses Puppeteer to run browsers that we archive in by loading pages, running behaviors such as auto-scroll, and then record the request/response traffic. We have some custom behavior for some social media and video sites to make sure that content is appropriate captured. It is a bit of a cat-and-mouse game as we have to continue to update these behaviors as sites change, but for the most part it works pretty well.

The trickier part is in replaying the archived websites, as a certain amount of re-writing has to happen in order to make sure the HTML and JS are working with archived assets rather than the live web. One implementation of this is replayweb.page (https://github.com/webrecorder/replayweb.page), which does all of the rewriting client-side in the browser. This sets you interact with archived websites in WARC or WACZ format as if interacting with the original site.

I use browsertrix-crawler[0] for crawling and it does well on JS heavy sites since it uses a real browser to request pages. Even has options to load browser profiles so you can crawl while being authenticated on sites.

[0] https://github.com/webrecorder/browsertrix-crawler

I have started using the tools from https://webrecorder.net like Browsertrix Crawler and they have been working great. The web archive format is open source and very portable. The crawler even crawls and saves YouTube videos embedded on pages which is awesome.

This looks like a good candidate for https://github.com/webrecorder/browsertrix-crawler.

I just learned about this organization, Saving Ukrainian Cultural Heritage Online (SUCHO): https://www.sucho.org/

They seem to be using various tools, like Browsertrix: https://github.com/webrecorder/browsertrix-crawler

It sounds promising for interactive sites:

> Support for custom browser behaviors, using Browsertix Behaviors including autoscroll, video autoplay and site-specific behaviors

Browsertrix links to https://replayweb.page/ for a way to view an archived site.

If you need more advanced recursive spider/crawling ability beyond --depth=1, check out Browsertrix, Photon, or Scrapy and pipe the outputted URLs into ArchiveBox.

I recommend this: https://github.com/webrecorder/browsertrix-crawler