Production Deployment Guide

This document outlines the steps required for deploying the Satoshi Port application to production, covering the Smart Contract, Frontend, and Backend components.

Contract Deployment

Prerequisites

• Private Keys: You need the private keys to deploy a new smart contract. Ask Sibi or Michael for access.

Deployment Steps

1. Trigger CI: Push a new tag to the develop branch.
2. Obtain Artifact: Wait for the CI job to complete. It will produce a new WASM file for the smart contract (see an example release).
3. Update Configuration: Update the contract version accordingly in the production.justfile.
4. Deploy: Run the following command to deploy the newer version of the contract:

   just prod::deploy
   

   Note: Ensure you handle any necessary state migration upgrades if applicable.

Frontend Deployment

Frontend deployment is managed using Cloudflare Pages.

• The main branch serves as the source of truth for production.
• To trigger a deployment, create a pull request for your changes to the main branch.

Backend Deployment

Backend deployments are managed via the devops repository.

Deployment Steps

1. Update the Docker image version in the kustomization.yaml file.
2. The deployment should then be synced via K3s ArgoCD.

Monitoring & Operations

• Documentation: For more details, refer to the Kube360 cluster documentation.
• Alerts: You should join the k3s-alertmanger Slack channel to monitor cluster alerts. Ask Sibi or Noris to be added to the channel.