Periodically, you will need to update configure and data files or install product updates for your on-premises (on-prem) deployment.
Updating Configuration and Data Files
If you modify configuration files or update data files or artifacts (for example, apply a new model update), then you will need to restart Docker services to get changes to take effect.
Log in to Docker:
Restart Docker services:
docker-compose -f /path/to/compose.yml -p deepgram up -d --force-recreate
Installing Product Updates
Deepgram periodically makes new product updates to the Docker images available. Some updates are recommended, while others are mandatory and, if not installed, will result in Deepgram products ceasing to function. To install product updates:
Contact Support to get the latest version numbers for the Deepgram API and Deepgram Engine images, and update your
Log in to Docker:
Download and apply product updates:
docker-compose -f /path/to/docker-compose.yml pull docker-compose -f /path/to/docker-compose.yml -p deepgram up -d
If you have ever been issued an on-prem license file for specialized, offline/air-gapped deployments, please contact your Deepgram Account Representative for additional documentation about maintaining your license.
Backing up Deepgram Products
When backing up a Deepgram installation, you should back up the following artifacts:
- directory housing the models that you use in your requests
We highly recommend backing up your whole server, if possible. Doing so will ensure that you can easily restore a running system.
Updated about 11 hours ago
Now that you understand how to maintain your deployed Deepgram on-premises system, it's time to take a look at best practices related to autoscaling your system based on demand.