Shane Kilkelly 9727c374b7 Update the readme with a short explanation of how this code works 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 8cae3f66c2 move contacts run file 8 лет назад
.gitignore dad3a74a7f add grunt cut task 10 лет назад
Dockerfile 56b2f641d2 Change launchpad location to github 8 лет назад
Dockerfile-base ff99e226bc Update texlive path 9 лет назад
Makefile 618c271039 Add a makefil 9 лет назад
README.md 9727c374b7 Update the readme with a short explanation of how this code works 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 3970b5b4be added trackChanges into features 8 лет назад

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.

Overall, this is very like how the services would run in production, it just happens to be all inside one docker container instead of being on one VM.