Skip to content

v0.8.0 · Cloud Deployment Blueprint

Pre-release
Pre-release

Choose a tag to compare

@HubertRonald HubertRonald released this 06 Jun 23:58
· 5 commits to main since this release
724fc61

Summary

This pre-release adds a sanitized Google Cloud deployment blueprint for VersoVector.

The milestone documents how the project could be deployed as a containerized emotional-semantic recommendation system using Cloud Run, Artifact Registry, Terraform, Docker services, and a future remote model artifact strategy.

This release keeps the public repository portfolio-ready while maintaining a clear boundary between public architecture documentation and private production infrastructure.

Highlights

  • Added a sanitized Terraform blueprint under:
infra/gcp-cloud-run-blueprint/
  • Added conceptual Google Cloud resources for:

    • Artifact Registry;
    • Cloud Run API service;
    • Cloud Run frontend service;
    • runtime service accounts;
    • public frontend access;
    • private API access from the frontend service account;
    • optional remote model artifact store configuration.
  • Added a public GCP architecture diagram:

figs/VersoVector-GCP-Architecture.png
  • Updated the main README with:

    • GCP deployment blueprint overview;
    • public vs private repository boundary;
    • updated repository structure;
    • additional documentation links;
    • infrastructure policy;
    • updated current status;
    • updated MLOps workflow phases.
  • Updated .gitignore to exclude Terraform local state and sensitive local configuration.

Public Repository Scope

This release keeps the public repository focused on:

architecture
demo frontend
FastAPI backend
Docker services
tests
documentation
sanitized Terraform blueprint

Private Production Scope

The following are intentionally excluded from the public repository:

real GCP project IDs
real IAM bindings
secrets
service account keys
billing configuration
authentication
premium access logic
analytics
production monitoring
private datasets
Terraform state
deployment environments

A real production deployment should live in a private repository or private environment-specific configuration, such as:

VersoVector-Platform

Blueprint Structure

infra/
└── gcp-cloud-run-blueprint/
    ├── README.md
    ├── main.tf
    ├── variables.tf
    ├── outputs.tf
    ├── versions.tf
    └── terraform.tfvars.example

Validation

Recommended Terraform validation:

cd infra/gcp-cloud-run-blueprint

terraform init
terraform fmt -recursive
terraform validate

Optional local plan:

cp terraform.tfvars.example terraform.tfvars
terraform plan -var-file=terraform.tfvars

Do not commit terraform.tfvars, .terraform/, or *.tfstate.

Pre-release Notice

This is a pre-release architecture and infrastructure blueprint milestone.

It does not deploy a production environment and does not include final Cloud Run deployment automation, real Artifact Registry configuration, production IAM, authentication, billing, monitoring, or GitHub Actions deployment workflows.

The goal is to document a credible public cloud architecture while keeping production infrastructure private and secure.