Miguel Serrano a818b1d427 Updated settings to serve minified assets (#110) 7 år sedan
..
init_scripts eadfb316b4 chown /var/www/ to www-data 9 år sedan
logrotate 81d99e968f add logrotate 10 år sedan
nginx af4703a2e2 remove proxy_set_header X-Forwarded-Proto $scheme for https 9 år sedan
runit 1df1f17fc6 Run filestore with node6 (#108) 7 år sedan
.dockerignore f100877eb7 Server Pro fixes (#109) 7 år sedan
.editorconfig 803f920b55 addressed PR comments 7 år sedan
.gitignore f100877eb7 Server Pro fixes (#109) 7 år sedan
Dockerfile 2bf86d8ea7 Revive overleaf community 7 år sedan
Dockerfile-base f100877eb7 Server Pro fixes (#109) 7 år sedan
Makefile 618c271039 Add a makefil 9 år sedan
README.md f100877eb7 Server Pro fixes (#109) 7 år sedan
git-revision.js 3e7595f3f2 add support for grunt build 10 år sedan
package.json ad30a56f0a Pin version of simple-git 8 år sedan
services.js 04579ce503 Pin contacts to branch 'sk-update-mongojs' 8 år sedan
settings.coffee a818b1d427 Updated settings to serve minified assets (#110) 7 år sedan

README.md

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.