Overleaf docs
Plans and pricingTemplatesUser docsGo to Overleaf
On-premises
On-premises
  • Welcome
    • Server Pro vs. Community Edition
  • Release notes
    • Release notes 5.x.x
      • Doc version recovery
    • Release notes 4.x.x
    • Release notes 3.x.x
      • Full project history migration
    • Release notes 2.x.x
    • Release notes 1.x.x
    • Release notes 0.x.x
  • Getting started
    • Before you start
    • Requirements
      • Skills needed
      • Hardware requirements
      • Software requirements
    • Microservices
    • Server Pro infrastructure
    • What is the Overleaf Toolkit?
  • Installation
    • Introduction
    • Using the Toolkit
      • 1: Download the Toolkit
      • 2: Familiarize yourself with the Toolkit
      • 3: Initialize the configuration
      • 4. Choose Community Edition or Server Pro
      • 5. Personalizing your instance
      • 6. Post-installation tasks
    • Air-gapped/offline deployments
    • Upgrading TeX Live
  • Configuration
    • Overleaf Toolkit
      • Files and locations
      • Toolkit settings
      • Environment variables
      • Server Pro-only configuration
        • LDAP
        • SAML 2.0
        • Sandboxed Compiles
        • Git integration
        • Templates
        • Adding LaTeX user help
      • Logging
      • TLS proxy
      • Branding
      • Localization
      • Email delivery
      • Redis
      • S3
  • Maintenance
    • docker-compose.yml to Toolkit migration
    • Upgrading your deployment
    • Data and backups
      • Exporting projects
    • Extending TeX Live
    • Horizontal scaling
    • S3 migration
    • Updating MongoDB
  • User and project management
    • User management
      • Username migration
    • Understanding license usage
    • Project management
  • Support
    • Project limits
    • Troubleshooting
    • Getting help
    • Support guides
      • Using templates as an individual
    • Overleaf user docs
Powered by GitBook
LogoLogo

Discover Overleaf

  • Home
  • Features

Solutions

  • Plans and pricing
  • For universities
  • For business
  • For government

Resources

  • Templates
  • User docs and LaTeX learning
  • Blog

© Overleaf

On this page
  • Enabling password authentication
  • Enabling Append-Only File Persistence

Was this helpful?

Export as PDF
  1. Configuration
  2. Overleaf Toolkit

Redis

PreviousEmail deliveryNextS3

Last updated 3 months ago

Was this helpful?

Enabling password authentication

If you're you're using an external Redis service and need to provide a password you can do this by setting the OVERLEAF_REDIS_PASS and REDIS_PASSWORD environment variables in the config/variables.env file and running the bin/up -d command to recreate the sharelatex container.

If you're running a local instance of Redis, you'll need to configure the redis service to start with password authentication. After setting the above environment variables, you'll also need to complete these additional steps:

  • Create a docker-compose.override.yml file in the config/ directory with the following content

services:
    redis:
        command: "redis-server --requirepass <YOUR-PASSWORD>"

If you have enable AOF persistence enabled, you'll need to add --appendonly yes to the command

  • Run bin/up -d to recreate the containers

Enabling Append-Only File Persistence

Redis AOF (Append-Only File) persistence provides a robust way to ensure data durability by logging every write operation received by the server. Unlike RDB snapshots, which take point-in-time copies of your dataset, AOF keeps a complete record of all changes made to your data.

Disabling RDB is optional. It's generally recommended that both persistence methods be used together. Before making any changes in production, we recommend reviewing the advantages and disadvantages of running AOF and RDB together.

You can read more about enabling AOF persistence in Redis here:

  1. Schedule a maintenance window for the upgrade.

  2. Stop the instance using bin/stop and take a backup of the config/ and data/ folders.

  3. Run bin/up to start the instance

  4. Run the command docker exec -it redis sh

  5. Run the command redis-cli to open the Redis command line interface

  6. In the redis-cli, run the command config set appendonly yes

  7. Now you'll need to wait for AOF rewrite to finish persisting the data. You can do that by typing INFO persistence into the redis-cli and waiting for aof_rewrite_in_progress and aof_rewrite_scheduled to be 0, and validating that aof_last_bgrewrite_status is ok.

  8. Exit the redis-cli by typing exit and pressing the return key

  9. Exit the redis container by typing exit and pressing the return key

  10. ​Run the command ls ./data/redis and confirm you can see the appendonly.aof file

  11. Edit the config/overleaf.rc file and change the REDIS_AOF_PERSISTENCE environment variable from false to true

  12. Run bin/up -d and make sure the application works (The project editor and history pane are functional).

https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/#how-i-can-switch-to-aof-if-im-currently-using-dumprdb-snapshots