Skip to content

Latest commit

 

History

History
81 lines (62 loc) · 2.38 KB

README.md

File metadata and controls

81 lines (62 loc) · 2.38 KB
Raw

Terraform for Dify on Google Cloud

Google Cloud Terraform

Dify GCP Architecture

日本語のREADME

Overview

This repository allows you to automatically set up Google Cloud resources using Terraform and deploy Dify in a highly available configuration.

Features

  • Serverless hosting
  • Auto-scaling
  • Data persistence

Prerequisites

  • Google Cloud account
  • Terraform installed
  • gcloud CLI installed
  • Required APIs enabled (Serverless VPC Access, Service Networking, etc.)

Configuration

  • Set environment-specific values in the terraform/environments/dev/terraform.tfvars file.
  • Create a GCS bucket to manage Terraform state in advance, and replace "your-tfstate-bucket" in the terraform/environments/dev/provider.tf file with the name of the created bucket.

Getting Started

  1. Clone the repository:

    git clone https://github.com/DeNA/dify-google-cloud-terraform.git

  2. Initialize Terraform:

    cd terraform/environments/dev
terraform init

  3. Make Artifact Registry repository:

    terraform apply -target=module.registry

  4. Build & push container images:

    cd ../../..
sh ./docker/cloudbuild.sh <your-region> <your-project-id>

    You can also specify a version of the dify-api image.

    sh ./docker/cloudbuild.sh <your-region> <your-project-id> <dify-api-version>

    If no version is specified, the latest version is used by default.

  5. Terraform plan:

    cd terraform/environments/dev
terraform plan

  6. Terraform apply:

    terraform apply

Cleanup

terraform destroy

Note: Cloud Storage, Cloud SQL, VPC, and VPC Peering cannot be deleted with the terraform destroy command. These are critical resources for data persistence. Access the console and carefully delete them. After that, use the terraform destroy command to ensure all resources have been deleted.

References

License

This software is licensed under the MIT License. See the LICENSE file for more details.