mserranom 2bf86d8ea7 Revive overleaf community пре 7 година
..
init_scripts eadfb316b4 chown /var/www/ to www-data пре 9 година
logrotate 81d99e968f add logrotate пре 10 година
nginx af4703a2e2 remove proxy_set_header X-Forwarded-Proto $scheme for https пре 9 година
runit 2bf86d8ea7 Revive overleaf community пре 7 година
.gitignore dad3a74a7f add grunt cut task пре 10 година
Dockerfile 2bf86d8ea7 Revive overleaf community пре 7 година
Dockerfile-base 2bf86d8ea7 Revive overleaf community пре 7 година
Makefile 618c271039 Add a makefil пре 9 година
README.md f8b3741292 remove bit from readme пре 7 година
git-revision.js 3e7595f3f2 add support for grunt build пре 10 година
package.json ad30a56f0a Pin version of simple-git пре 8 година
services.js 04579ce503 Pin contacts to branch 'sk-update-mongojs' пре 8 година
settings.coffee 2bf86d8ea7 Revive overleaf community пре 7 година

README.md

ShareLaTeX Docker Image

This is the source for building the sharelatex 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 image extends the base image and adds the actual sharelatex code and services.

Use make build-base and make build-community to build these images.

How the Sharelatex code gets here

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

That repo is cloned down into the docker image, and a script then installs all the services. This way of doing things predates the new dev-env, and isn't currently tested.

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 sharelatex services. Baseimage uses the runit service manager to manage services, and we add our init-scripts from the ./runit folder.