A web-based collaborative LaTeX editor
Find a file
2019-10-15 11:00:38 +02:00
init_scripts
logrotate
nginx
runit Delete aggregated error log (#117) 2019-10-08 11:54:49 +02:00
.dockerignore Added debugging support to services (#113) 2019-09-10 17:13:17 +02:00
.editorconfig addressed PR comments 2019-08-08 10:44:14 +00:00
.gitignore Server Pro fixes (#109) 2019-08-22 16:57:26 +02:00
Dockerfile Linked CLSI synctext to /opts/synctex (#118) 2019-10-08 12:47:08 +02:00
Dockerfile-base Added debugging support to services (#113) 2019-09-10 17:13:17 +02:00
git-revision.js
Makefile
package.json Pin version of simple-git 2018-01-22 14:47:00 +00:00
README.md Server Pro fixes (#109) 2019-08-22 16:57:26 +02:00
services.js
settings.coffee Disable project-history via settings (#125) 2019-10-15 11:00:38 +02:00

Overleaf Docker Image

This is the source for building the Overleaf community-edition docker image.

End-User Install

Please see the offical wiki for install guides

Development

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 and aspell, 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 to build these images.

How the Overleaf code gets here

This repo uses the public Overleaf repository, which used to be the main public source for the Overleaf system.

That repo is cloned down into the docker image, and a script then installs all the services.

How services run inside the container

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 ./runit folder.