Bez popisu

Shane Kilkelly e448cad7ce Merge pull request #98 from sharelatex/sk-update-readme před 7 roky
init_scripts 4283bde9c0 chown /var/www/ to www-data před 10 roky
logrotate 10b6f88f3b add logrotate před 10 roky
nginx 8c08df2717 remove proxy_set_header X-Forwarded-Proto $scheme for https před 9 roky
runit 51d59f20b0 move contacts run file před 9 roky
.gitignore d4fb706ac0 add grunt cut task před 10 roky
Dockerfile 3c4866a710 Change launchpad location to github před 8 roky
Dockerfile-base 5825a51c44 Update texlive path před 9 roky
Makefile d739373892 Add a makefil před 9 roky
README.md e359037958 remove bit from readme před 7 roky
git-revision.js f33ea04408 add support for grunt build před 10 roky
package.json d5338b5719 Pin version of simple-git před 8 roky
services.js 2761615440 Pin contacts to branch 'sk-update-mongojs' před 9 roky
settings.coffee f18a0498a9 added trackChanges into features před 8 roky

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.