Self-hosting Apidog
  1. Configuration
Self-hosting Apidog
  • Installation
    • Installation Overview
    • Obtaining Apidog On-premises License
    • Running Apidog on Docker
    • Running Apidog on Kubernetes
    • Running Apidog Multi-Container Deployment without Kubernetes
    • Admin Panel
    • Installing Apidog Client
    • Backing up Apidog
    • Renewing Apidog
    • Updating Apidog
    • Supported browsers
    • Privacy
  • Configuration
    • Environment Variables
    • Configuring the application database
    • Configuring the application storage service
    • Using LDAP for authentication
    • Using OKTA for authentication
    • Using OAuth2.0 for authentication
  • Apidog API (coming soon)
  • Troubleshooting
    • Troubleshooting
    • FAQ
  1. Configuration

Configuring the application storage service

The Application Storage Service is tasked with the storage of static resources uploaded by users. These resources include, but are not limited to, team test reports, project icons, and images embedded in Markdown documents.

Built-in storage service#

Apidog comes with a default storage service that utilizes the file system. It's important to note that if the container is removed, all Apidog application data stored within it will be lost.
To ensure data persistence beyond the lifespan of the container, a local file path can be mounted within the container.
Upon launching the container, Apidog will mount the specified folder from your local filesystem into the container.

Amazon S3 and other S3-compatible storage services#

You can also use Amazon S3 as the storage service. To do so, you need to provide the following environment variables:
Other S3-compatible storage services, such as MinIO and Cloudflare R2, can also be used due to their compatibility with the S3 API.
Additional optional environment variables can be located in the Environment variables configuration guide.
Previous
Configuring the application database
Next
Using LDAP for authentication
Built with