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
137 commits 9 branches 0 tags 1.2 MiB
Find a file
Miguel Serrano e39aa84e7f
Improve messaging on upgrade scripts 
Clears some ambiguity about whether "proceed" means doing a backup or actually upgrading SP.
2022-09-22 12:13:39 +02:00
.github added github Issue and PR templates for contributions 2020-10-02 12:32:22 +02:00
bin Improve messaging on upgrade scripts 2022-09-22 12:13:39 +02: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 Add docs and default config for SHARELATEX_LISTEN_IP (#105) 2022-08-16 11:33:58 +02:00
lib Updated config seed to use TexLive 2022 2022-09-22 12:02:00 +02:00
.gitignore Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
CHANGELOG.md Add docs and default config for SHARELATEX_LISTEN_IP (#105) 2022-08-16 11:33:58 +02:00
LICENSE Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
README.md Link to CONTRIBUTING file in the main overleaf repository 2022-07-24 21:37:19 +01:00

README.md

Overleaf Toolkit

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).

The Developer wiki contains further documentation on releases, features and other configuration elements.

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.