46aab91ef5
This has been bugging me for a while — any type of repetitive action that shows a toast will quickly cause a big stack of toasts to build up. This fixes that by allowing different categories of toasts to exist, where each category can only have one active toast. _Different_ categories of toast can coexist just fine, but toasts with the same `id` will replace any existing toast with that same `id`. It's been a pet peeve for a while, and it should make any sort of "power user" use of Browsertrix a lot nicer :) I've gone over all the existing toasts and applied what feel like decent differentiations, but I'm not set on any of them — open to suggestions! https://github.com/user-attachments/assets/dbe39141-9e56-427d-b702-124c45ef2b9a --------- Co-authored-by: Ilya Kreymer <ikreymer@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| ansible | ||
| assets | ||
| backend | ||
| chart | ||
| configs | ||
| frontend | ||
| scripts | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| btrix | ||
| CHANGES.md | ||
| LICENSE | ||
| NOTICE | ||
| pylintrc | ||
| README.md | ||
| update-version.sh | ||
| version.txt | ||
Browsertrix is a 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 webrecorder.net/browsertrix for a feature overview and information about how to sign up for Webrecorder's hosted Browsertrix service.
Documentation
The full docs for using, deploying, and developing Browsertrix are available at docs.browsertrix.com.
Our docs are created with Material for MKDocs.
Deployment
The latest deployment documentation is available at docs.browsertrix.com/deploy.
The docs cover deploying Browsertrix in different environments using Kubernetes, from a single-node setup to scalable clusters in the cloud.
Early on, Browsertrix also supported Docker Compose and podman-based deployment. This was 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.
Contributing
Though the system and backend API is fairly stable, we are working on many additional features. Please see the GitHub issues and this GitHub Project for our current project plan and tasks.
Guides for getting started with local development are available at docs.browsertrix.com/develop.
Translation
We use Weblate to manage translation contributions.
License
Browsertrix is made available under the AGPLv3 License.
Documentation is made available under the Creative Commons Attribution 4.0 International License