docs: update deployment templates to just pull the docker image #445
Conversation
…oot that instead of building
cloud-deployments/digitalocean/terraform/main.tfHardcoding sensitive information such as API tokens in your code can lead to security vulnerabilities if the code is exposed or shared. It's recommended to use environment variables or secure vaults to store such sensitive information. provider "digitalocean" {
token = var.do_token
}cloud-deployments/gcp/deployment/gcp_deploy_anything_llm.yamlPulling the latest Docker image can lead to unexpected behavior if the latest version introduces breaking changes. It's recommended to pull a specific version of the Docker image to ensure the stability and performance of your application. # Pull the specific version of the Docker image
sudo docker pull mintplexlabs/anythingllm:v1.0.0 |
| sudo docker pull mintplexlabs/anythingllm:master | ||
| sudo docker run -d -p 3001:3001 -v /home/anythingllm:/app/server/storage -v /home/anythingllm/.env:/app/server/.env -e STORAGE_DIR="/app/server/storage" mintplexlabs/anythingllm:master |
There was a problem hiding this comment.
Pulling the latest Docker image can lead to unexpected behavior if the latest version introduces breaking changes. It's recommended to pull a specific version of the Docker image to ensure the stability and performance of your application.
| sudo docker pull mintplexlabs/anythingllm:master | |
| sudo docker run -d -p 3001:3001 -v /home/anythingllm:/app/server/storage -v /home/anythingllm/.env:/app/server/.env -e STORAGE_DIR="/app/server/storage" mintplexlabs/anythingllm:master | |
| sudo docker pull mintplexlabs/anythingllm:v1.0.0 | |
| sudo docker run -d -p 3001:3001 -v /home/anythingllm:/app/server/storage -v /home/anythingllm/.env:/app/server/.env -e STORAGE_DIR="/app/server/storage" mintplexlabs/anythingllm:v1.0.0 |
…plex-Labs#445) docs: update deployment templates to just pull the docker image and boot that instead of building
No description provided.