f671c3dc59
* [web] read a linked project file's source from history Behind the `linked-file-from-history` flag, a linked `project_file` import reads the source out of the source project's latest history snapshot rather than out of its file tree in mongo, where docs and files are two kinds of thing. - `ProjectFileAgent` gains `_importFromHistory` alongside the existing `_importFromProject`, and the flag picks between them. The snapshot only holds what has reached history, so the source project is flushed through document-updater and project-history first. A file that is editable is loaded eagerly, which applies the edit operations sitting on top of its blob; one that is not keeps its hash and is streamed. The file is promisified on the way. - `History/HistoryOTContentManager.mjs` reads the latest chunk and rolls its changes into a snapshot, retrying the read. `History/HistoryBlobStore.mjs` is the blob store overleaf-editor-core asks for while loading a file. - `LinkedFilesController` resolves the flag, including from the referer: the import endpoints have no query string of their own. Every agent takes the assignment so that the ones that do not read it still pass it along. - `linked-file-from-history.spec.ts` drives the flag from the editor url, over three imports from another project: a file uploaded to the source project and then refreshed from it, an edit the source project has only made in its editor, and a binary file. Both sources produce the same file, so which one was read is asserted in the acceptance tests rather than here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * [saas-e2e] add test coverage for tracked-delete in linked file source * Apply suggestions from code review Co-authored-by: Mathias Jakobsen <mathias.jakobsen@overleaf.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Mathias Jakobsen <mathias.jakobsen@overleaf.com> GitOrigin-RevId: 3907d6d399e4b5315e68bf833663c06bc72f4011
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.