All apps · 0 apps
Overleaf
OfficialDocker app from Selfhosters
Overview
Readme
View on GitHubOverleaf Docker Image
THIS REPOSITORY HAS BEEN MERGED INTO https://github.com/overleaf/overleaf .
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.
Install Overleaf on Unraid in a few clicks.
Find Overleaf in Community Apps on your Unraid server, review the template, and click Install. Unraid handles the Docker app or plugin setup from the published template.
Categories
Download Statistics
Total Downloads Over Time
Related apps
Explore more like this
Explore allLinks
Details
sharelatex/sharelatexRuntime arguments
- Web UI
http://[IP]:[PORT:80]- Network
bridge- Shell
sh- Privileged
- false
Template configuration
WebUI HTTP port
- Target
- 80
- Default
- 80
The name to display when talking about the running app. Defaults to 'Overleaf (Community Edition)'.
Set the tab title of the application
Where your instance of Overleaf is publicly available. This is used in public links, and when connecting over websockets, so must be configured correctly!
The email address where users can reach the person who runs the site.
The host name of the Redis instance to use
The port of the Redis instance to use
The password to use when connecting to Redis (if applicable)
The URL of the Mongo database to use
Set to true if running behind a proxy like nginx/apache allowing it to correctly detect the forwarded IP address
A random string which is used to secure tokens, if load balancing this needs to be set to the same toke across boxes. If only 1 instance is being run it does not need to be set by the user.
Set this to something non-zero to use a secure cookie. Only use this if your Overleaf instance is running behind a reverse proxy with SSL configured.
If set to true, will restrict project invites to email addresses which correspond with existing user accounts.
If set to 'true', will allow non-authenticated users to view the site. The default is false, which means non-authenticated users will be unconditionally redirected to the login page when they try to view any part of the site. Note, setting this option does not disable authentication or security in any way. This option is necessary if your users intend to make their projects public and have non-authenticated users view those projects.
If set to 'true', will allow anonymous users to view and edit projects shared via the new link-sharing feature.