Skip to main content
The ayakaleaf toolkit is the recommended deployment method for on-premises installations of the Community Edition, Ayakaleaf Pro, it has been designed to work with the most common environment: a single physical server or virtual machine. The Toolkit uses docker compose to manage your server’s Docker containers and provides a set of scripts which wrap docker commands to assist with the more technical side of managing an on-premises version of Overleaf.

​
The bin/docker-compose wrapper

The bin/docker-compose script is a wrapper around docker compose. It loads configuration from the config/ directory, before invoking docker compose with whatever arguments were passed to the script. You can treat bin/docker-compose as a transparent wrapper for the docker compose program installed on your machine. Example:
Check running containers

​
Convenience helpers

In addition to bin/docker-compose, the Toolkit provides convenient scripts to assist with common tasks:
  • bin/up: shortcut for bin/docker-compose up
  • bin/start: shortcut for bin/docker-compose start
  • bin/stop: shortcut for bin/docker-compose stop
  • bin/shell: starts a shell inside the sharelatex container
  • bin/doctor: script used to gather installation and deployment information. See the “Checking your server” section below
  • bin/mongo: starts a shell inside the mongo container and switches to the correct database (sharelatex)
  • bin/backup-config: create a copy (zip or tar) of your current configuration and store it in a destination directory of your choice
  • bin/logs: view/tail service logs
  • bin/error-logs: view/tail service error logs
  • bin/rename-env-vars-5-0: migration script to update environment variables in config/variables.env (re-branding from ShareLaTeX to Overleaf)
  • bin/rename-rc-vars: migration script to update environment variables in config/overleaf.rc (re-branding from ShareLaTeX to Overleaf)
  • bin/run-script: helper to simplify running scripts stored within the sharelatex container
  • bin/upgrade: assists with instance upgrades. The script will check for Toolkit updates (via git) and offer to pull changes, check for the latest Docker image version and offer to update it. It provides step-by-step confirmation, the option to back up current configuration, and handles stopping/starting Docker services. See Upgrading your deployment for more information: https://docs.overleaf.com/on-premises/maintenance/upgrading-your-deployment
If you prefer to run your instance without attaching to the Docker logs you can run bin/up -d to run in detached mode.

​
Checking your server

The Overleaf Toolkit includes a handy script called bin/doctor that produces a report pointing to any unfulfilled dependency. Before continuing, run the bin/doctor script and check that everything is working correctly:
Run Overleaf Doctor
Example output (truncated/illustrative):
If any dependencies are missing, the doctor will print warnings. If you run into problems, first run bin/doctor and check its output for warnings.
In both cases, include the output of bin/doctor in your message.
Last modified on October 4, 2026