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
209 commits 9 branches 0 tags 1.2 MiB
Find a file
Eric Mc Sween 9f5bd17cda Removed OAuth2 client configuration 
Now that the git bridge exclusively uses personal access tokens in
ServerPro, it doesn't need to perform a password grant request and
therefore doesn't need to have its OAuth client id and secret
configured.
2023-05-24 16:15:28 -04:00
.github added github Issue and PR templates for contributions 2020-10-02 12:32:22 +02:00
bin Removed OAuth2 client configuration 2023-05-24 16:15:28 -04: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 Documentation fixes 2023-05-17 14:16:55 -04:00
lib Removed OAuth2 client configuration 2023-05-24 16:15:28 -04:00
.gitignore Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
CHANGELOG.md Documentation fixes 2023-05-17 14:16:55 -04:00
LICENSE Public release of the Overleaf Toolkit 2020-08-19 13:31:17 +01:00
README.md Make git clone commands match 2022-10-12 09:52:12 +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-toolkit

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.