mirrors/overleaf-toolkit
1
0
Fork 0
mirror of https://github.com/overleaf/toolkit.git synced 2025-04-19 07:18:06 +02:00
Code Activity
No description
11 commits 9 branches 0 tags 1.2 MiB
Find a file
Shane Kilkelly 3fda5d0ae0 Add SHARELATEX_PORT option, default to 80 
This allows a user to configure the host port that the sharelatex
container will bind to. Previously this was hard-coded to port 80, which
can cause problems on systems with something already bound to that port.
2020-10-08 09:40:53 +01:00
.github added github Issue and PR templates for contributions 2020-10-02 12:32:22 +02:00
bin Add SHARELATEX_PORT option, default to 80 2020-10-08 09:40:53 +01:00
config Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
data Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
doc Update quick-start-guide.md 2020-10-02 09:14:20 +02:00
lib Add SHARELATEX_PORT option, default to 80 2020-10-08 09:40:53 +01:00
.gitignore Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
CONTRIBUTING Create CONTRIBUTING 2020-10-02 11:11:11 +01:00
LICENSE Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
README.md Update README.md 2020-10-02 11:12:12 +01:00

README.md

Overleaf Toolkit

(Note: this software is currently in beta testing. Functionality and documentation may be incomplete)

This repository contains the Overleaf Toolkit, the standard tools for running a local instance of Overleaf. This toolkit will help you to set up and administer both Overleaf Community Edition (free to use, and community supported), and Overleaf Server Pro (commercial, with professional support).

Getting Started

Clone this repository locally:

git clone https://github.com/overleaf/toolkit.git ./overleaf

Then follow the Quick Start Guide.

Documentation

See Documentation Index

Contributing

See the CONTRIBUTING file.

Getting Help

Users of the free Community Edition should open an issue on github.

Users of Server Pro should contact support@overleaf.com for assistance.

In both cases, it is a good idea to include the output of the bin/doctor script in your message.