b2d4687c52
* Update test script to allow coverage to be recorded * Collect coverage in CI * [web] integrate coverage report with Jenkins * [web] add coverage report for acceptance tests * Use --all flag in vitest coverage * Use --all flag in acceptance tests * Switch vitest to use istanbul * Bump versions of vitest plugins and update package-lock.json * [web] use a dedicated parameter for coverage in unit/acceptance tests * [web] temporarily generate HTML report and archive artifacts * [web] do not run acceptance tests as root in CI * [web] increase hook timeout in vitest when collecting coverage * [web] exclude packageMapping from coverage report * [web] use relative paths in clover reports * [web] reduce concurrency for unit tests in CI * [web] keep source code forever on builds * Revert "[web] temporarily generate HTML report and archive artifacts" This reverts commit 4c9db571 * [web] archive all the raw coverage report files * [monorepo] update build scripts for web * [monorepo] update package-lock.json after merge * [web] remove spurious change * [web] merge Jenkins parameter sections * [web] increase hookTimeout when collecting coverage report --------- Co-authored-by: Jakob Ackermann <jakob.ackermann@overleaf.com> GitOrigin-RevId: 9f1ec6d38a7b037267737bec3b0bc53a0ac844af
An open-source online real-time collaborative LaTeX editor.
Wiki • Server Pro • Contributing • Mailing List • Authors • License
Figure 1: A screenshot of a project being edited in Overleaf Community Edition.
Community Edition
Overleaf is an open-source online real-time collaborative LaTeX editor. We run a hosted version at www.overleaf.com, but you can also run your own local version, and contribute to the development of Overleaf.
Caution
Overleaf Community Edition is intended for use in environments where all users are trusted. Community Edition is not appropriate for scenarios where isolation of users is required due to Sandbox Compiles not being available. When not using Sandboxed Compiles, users have full read and write access to the
sharelatexcontainer resources (filesystem, network, environment variables) when running LaTeX compiles.
For more information on Sandbox Compiles check out our documentation.
Enterprise
If you want help installing and maintaining Overleaf in your lab or workplace, we offer an officially supported version called Overleaf Server Pro. It also includes more features for security (SSO with LDAP or SAML), administration and collaboration (e.g. tracked changes). Find out more!
Keeping up to date
Sign up to the mailing list to get updates on Overleaf releases and development.
Installation
We have detailed installation instructions in the Overleaf Toolkit.
Upgrading
If you are upgrading from a previous version of Overleaf, please see the Release Notes section on the Wiki for all of the versions between your current version and the version you are upgrading to.
Overleaf Docker Image
This repo contains two dockerfiles, Dockerfile-base, which builds the
sharelatex/sharelatex-base image, and Dockerfile which builds the
sharelatex/sharelatex (or "community") image.
The Base image generally contains the basic dependencies like wget, plus texlive.
We split this out because it's a pretty heavy set of
dependencies, and it's nice to not have to rebuild all of that every time.
The sharelatex/sharelatex image extends the base image and adds the actual Overleaf code
and services.
Use make build-base and make build-community from server-ce/ to build these images.
We use the Phusion base-image
(which is extended by our base image) to provide us with a VM-like container
in which to run the Overleaf services. Baseimage uses the runit service
manager to manage services, and we add our init-scripts from the server-ce/runit
folder.
Contributing
Please see the CONTRIBUTING file for information on contributing to the development of Overleaf.
Authors
License
The code in this repository is released under the GNU AFFERO GENERAL PUBLIC LICENSE, version 3. A copy can be found in the LICENSE file.
Copyright (c) Overleaf, 2014-2025.