Go to file
Tessa Walsh 14b349443f
Make pending invites expire via TTL index (#568)
* Make invites expire after configurable window

The value can be set in EXPIRE_AFTER_SECONDS env var and via
helm chart values, and defaults to 7 days.

* Create nightly test CI and add invite expiration test to it

* Update 404 error message for missing or expired invite

---------

Co-authored-by: sua yoo <sua@suayoo.com>
2023-02-14 16:07:14 -05:00
.github/workflows Make pending invites expire via TTL index (#568) 2023-02-14 16:07:14 -05:00
ansible add/remove admin node pool (#556) 2023-02-04 19:17:05 -08:00
backend Make pending invites expire via TTL index (#568) 2023-02-14 16:07:14 -05:00
chart Make pending invites expire via TTL index (#568) 2023-02-14 16:07:14 -05:00
configs Remove Code and Configs for Swarm/podman support (#407) 2022-12-08 18:19:58 -08:00
docs docs: tweak ansible deployment docs 2023-01-11 22:33:28 -08:00
frontend Make pending invites expire via TTL index (#568) 2023-02-14 16:07:14 -05:00
scripts VNC-Based Profile Browser (#433) 2023-01-10 14:42:42 -08:00
test Single config and env vars (#267) 2022-06-16 21:50:03 -07:00
.gitignore add digital ocean documentation (#421) 2023-01-11 21:57:17 -08:00
.pre-commit-config.yaml Rename archives/teams -> orgs in codebase + add db migration (#486) 2023-01-18 14:51:04 -08:00
CHANGES.md docs: CHANGES: fix typo, begin changelist for 1.2.0 (#410) 2022-12-12 20:32:35 -08:00
LICENSE Add License, Logo and README updates for release (#157) 2022-02-23 12:10:46 -08:00
mkdocs.yml Minor docs style updates (#409) 2022-12-12 18:15:12 -08:00
NOTICE Add License, Logo and README updates for release (#157) 2022-02-23 12:10:46 -08:00
pylintrc
README.md chore(typo): fix typo in read me 2023-02-03 18:32:58 +00:00
update-version.sh Release Build + Versioning (#373) 2022-11-18 17:15:25 -08:00
version.txt bump version to 1.2.1-beta.0 2023-02-05 12:27:45 -08:00

Browsertrix Cloud

Browsertrix Cloud 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 Features for a high-level list of planned features.

Documentation

The full docs for using, deploying and developing Browsertrix Cloud 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 Cloud in different environments using Kubernetes, from a single-node setup to scalable clusters in the cloud.

Previously, Browsertrix Cloud also supported Docker Compose and podman-based deployment. This is now 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 Cloud 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 Cloud 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/dev

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

License

Browsertrix Cloud is made available under the AGPLv3 License.

If you would like to use it under a different license or have a question, please reach out as that may be a possibility.