Proksi
  • 🚀General
    • Getting started
    • Performance
    • Motivations
    • Specifications
  • 💾Installation
    • Docker
    • Single binary
  • 📚Configuration
    • HCL
      • Functions
    • YAML
    • ENV
    • Logging
    • Auto Reload
    • Daemon
    • Redis
  • 🔀Routing
    • Upstreams
    • Headers
  • 🧩Plugins
    • Request ID
    • Basic Auth
    • OAuth2
  • đŸ“Ŋī¸Use cases
    • Cache
    • Docker swarm
  • đŸ›Šī¸Contributing
    • Repository
  • Github
  • Crates.io
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Configuration

Redis

Use Redis/Dragonfly to store certificates, and distribute Proksi instances across multiple servers.

Most use cases require a distributed configuration setup. This can be achieved by using Redis or Dragonfly as a distributed cache for storing certificates and distributing Proksi instances across multiple servers.

Redis Configuration

To configure Proksi to use Redis as a distributed cache, you can set the following in your proksi.hcl file:

proksi.hcl
store {
  store_type = "redis"
  redis_url = "redis://localhost:6379"
}

This will then use Redis as backend storage for certificates, challenges and even raw routing configuration. There's a penalty in terms of performance, but it's worth it for the benefits of scalability and reliability.

PreviousDaemonNextUpstreams

Last updated 24 days ago

Was this helpful?

📚