Go to file
Tessa Walsh d31bdd2a21
Change resource table to be based on mime type (#1698)
Follow-up to #1689 

Instead of just using resource types, using a combination of mime type, resource type and extension analysis.
Current logic is:
    - if resourceType is script, stylesheet, image, font, use that definitely
    - if resourceType is fetch/xhr, also check for extension, specifically for images
    - categorize favicon.ico separately as 'favicon'
    - also check for extension for json
    - also check for pdf by type + extension
    - categorize 'ping' as 'other'
    - by default, use the first part of mime as the type
2024-04-20 19:02:15 -07:00
.github Run crawler and profilebrowser with non-root user (#1625) 2024-04-17 12:03:33 -07:00
.vscode Initial QA Review UI! (#1624) 2024-04-04 15:09:52 -07:00
ansible Bump cryptography from 41.0.1 to 42.0.4 in /ansible (#1574) 2024-03-06 16:24:36 -08:00
assets Frontend: App Branding! (#1592) 2024-04-17 23:40:02 -04:00
backend Update tests with latest crawler (#1711) 2024-04-20 15:56:26 -07:00
chart Update tests with latest crawler (#1711) 2024-04-20 15:56:26 -07:00
configs
docs Add post load delay to Browsertrix (#1700) 2024-04-18 20:03:47 -07:00
frontend Change resource table to be based on mime type (#1698) 2024-04-20 19:02:15 -07:00
scripts publish helm chart on release (fixes #1114) (#1117) (#1123) 2023-08-30 12:02:02 -07:00
test
.gitignore
.pre-commit-config.yaml Format backend with Black 24 (#1507) 2024-02-07 11:35:34 -08:00
btrix Add setup command to btrix helper to copy local config (#1462) 2024-01-10 19:32:39 -08:00
CHANGES.md
LICENSE
mkdocs.yml Docs: Update docs theme (#1594) 2024-03-16 15:09:31 -07:00
NOTICE
pylintrc
README.md Frontend: App Branding! (#1592) 2024-04-17 23:40:02 -04:00
update-version.sh enable screenshots by default + fix py version formatting (#1518) 2024-02-07 17:07:28 -08:00
version.txt version: bump to 1.10.0-beta.1 2024-04-05 18:24:14 -07:00
yarn.lock

Browsertrix

 

Browsertrix is an open-source cloud-native high-fidelity browser-based crawling service designed to make web archiving easier and more accessible for everyone.

The service provides an API and UI for scheduling crawls and viewing results, and managing all aspects of crawling process. This system provides the orchestration and management around crawling, while the actual crawling is performed using Browsertrix Crawler containers, which are launched for each crawl.

See browsertrix.com for a feature overview and information about Browsertrix hosting.

Documentation

The full docs for using, deploying, and developing Browsertrix are available at: https://docs.browsertrix.cloud

Deployment

The latest deployment documentation is available at: https://docs.browsertrix.cloud/deploy

The docs cover deploying Browsertrix in different environments using Kubernetes, from a single-node setup to scalable clusters in the cloud.

Previously, Browsertrix also supported Docker Compose and podman-based deployment. This has been deprecated due to the complexity of maintaining feature parity across different setups, and with various Kubernetes deployment options being available and easy to deploy, even on a single machine.

Making deployment of Browsertrix as easy as possible remains a key goal, and we welcome suggestions for how we can further improve our Kubernetes deployment options.

If you are looking to just try running a single crawl, you may want to try Browsertrix Crawler first to test out the crawling capabilities.

Development Status

Browsertrix is currently in a beta, though the system and backend API is fairly stable, we are working on many additional features.

Additional developer documentation is available at https://docs.browsertrix.cloud/develop

Please see the GitHub issues and this GitHub Project for our current project plan and tasks.

License

Browsertrix is made available under the AGPLv3 License.

Documentation is made available under the Creative Commons Attribution 4.0 International License