legacy-api

Backend API code for sejiwo.com

How Sejiwo Works

Sejiwo is an automated digital will service that delivers your final message to loved ones only if you become unresponsive.

flowchart LR
    A[User Creates Will] --> B[Set Recipients]
    B --> C[Configure Timing]
    C --> D[System Activated]
    
    D --> E{Periodic Check}
    E -->|User Responds| F[Timer Reset]
    E -->|No Response| G[Auto Delivery]
    
    F --> E
    G --> H[Message Delivered]
    
    style A fill:#2563eb,stroke:#1e40af,stroke-width:2px,color:#ffffff
    style B fill:#6366f1,stroke:#4f46e5,stroke-width:2px,color:#ffffff
    style C fill:#8b5cf6,stroke:#7c3aed,stroke-width:2px,color:#ffffff
    style D fill:#06b6d4,stroke:#0891b2,stroke-width:2px,color:#ffffff
    style E fill:#64748b,stroke:#475569,stroke-width:2px,color:#ffffff
    style F fill:#10b981,stroke:#059669,stroke-width:2px,color:#ffffff
    style G fill:#f59e0b,stroke:#d97706,stroke-width:2px,color:#ffffff
    style H fill:#ec4899,stroke:#db2777,stroke-width:2px,color:#ffffff
    
    classDef default font-size:14px,font-weight:500

Key Features:

⏰ Automatic Delivery: Messages delivered only when you don't respond to reminders
🔒 Secure: AES encrypted message storage
📧 Flexible Recipients: Send to up to 3 people
🔄 Stay in Control: Easy to postpone or cancel anytime
⚡ Set and Forget: Fully automated once configured

📋 View Technical Architecture & System Details

Prerequisites

Go 1.24
Postgresql 17.6
sqlc (Optional, for generating db structs from data/schema.sql & data/query.sql)
pgAdmin4 (Optional, to manage the database or use psql instead)
gcloud cli (Optional, for deploying the api to Google Cloud Platform)

Development

Database setup

After installing go & postgresql

./init-db.sh # Prepare dev database - set proper passwords & secrets for production

Testing

This is integration test, you will need to run the database first before running the test

cp .env-test-template.yaml .env-test.yaml
go test ./...

Why do I use template config? Because I put secrets in my .env-test.yaml & I don't want to accidentally commit it. Please let me know how to do it better.

Running the app in localhost

From the root directory of this repo

# You need to specify the env because the default value is "test"
# and I use the env to customize static file directories
ENVIRONMENT=dev go run cmd/main.go # Or just use vscode debug feature

API call examples

Install thunder client, a vscode extension similar to postman
Import thunder-collection_legacy-api.json from thunder client

Deployment

Create the secrets needed to run the apps

echo -n "PUT_THE_DB_PASSWORD_HERE" | \
  gcloud secrets create "db_password" --replication-policy "automatic" --data-file -

# This one needs to be exactly 69 characters length
echo -n "PUT_THE_STATIC_SECRET_HERE" | \
  gcloud secrets create "static_secret" --replication-policy "automatic" --data-file -

# 32 characters length for AES encryption
echo -n "PUT_THE_ENCRYPTION_KEY_HERE" | \
  gcloud secrets create "encryption_key" --replication-policy "automatic" --data-file -

# Additional SSL cert for Supabase
# Download from https://supabase.com/docs/guides/database/connecting-to-postgres#connecting-with-ssl
cat prod-ca-2021.crt | \
  gcloud secrets create "supabase_ssl_certificate" --replication-policy "automatic" --data-file -

# To send emails
echo -n "PUT_THE_MAILJET_API_KEY_HERE" | \
  gcloud secrets create "mailjet_api_key" --replication-policy "automatic" --data-file -

# To send emails
echo -n "PUT_THE_MAILJET_SECRET_KEY_HERE" | \
  gcloud secrets create "mailjet_secret_key" --replication-policy "automatic" --data-file -

Give the secret manager read access to your project service account.

gcloud projects add-iam-policy-binding [YOUR_GCLOUD_PROJECT_NAME] --member='serviceAccount:[YOUR_GCLOUD_PROJECT_NAME]@appspot.gserviceaccount.com' --role='roles/secretmanager.secretAccessor'

Prepare the DB Connect to supabase: https://supabase.com/docs/guides/database/connecting-to-postgres#direct-connections Then using psql or pgAdmin:

##################################################################
# Copy paste the query in data/seed.sql, edit the PASSWORD field #
##################################################################

# Switch to project_legacy database
\c project_legacy

###########################################
# Copy paste the query in data/schema.sql #
###########################################

Deploy the Cloud Run service

# Copy env
cp .env-prod-template.yaml .env-prod.yaml
# Then edit the .env-prod.yaml, follow the comments provided in the file

gcloud run deploy legacy-api --source . \
  --region=asia-southeast1 --allow-unauthenticated --timeout 15s \
  --min-instances 0 --max-instances 100 --cpu 1 --memory 128Mi \
  --set-secrets DB_PASSWORD=db_password:latest,STATIC_SECRET=static_secret:latest,ENCRYPTION_KEY=encryption_key:latest,MAILJET_API_KEY=mailjet_api_key:latest,MAILJET_SECRET_KEY=mailjet_secret_key:latest \
  --env-vars-file .env-prod.yaml --update-labels service=legacy --tag=main

Deploy the scheduler

# Create a pub/sub topic - this might take a while
gcloud pubsub topics create project-legacy-scheduler

# Create a google cloud scheduler
gcloud scheduler jobs create pubsub SendReminderMessages --location asia-southeast1 --schedule "22 19 * * *" \
  --topic project-legacy-scheduler --attributes action=send-reminder-messages \
  --description "Send reminder messages daily" --time-zone "Asia/Jakarta"
gcloud scheduler jobs create pubsub SendTestaments --location asia-southeast1 --schedule "38 19 * * *" \
  --topic project-legacy-scheduler --attributes action=send-testaments \
  --description "Send reminder messages daily" --time-zone "Asia/Jakarta"

# Copy env
cp .env.prod-cloud-function-template.yaml .env-prod-cloud-function.yaml

# CloudFunctionForSchedulerWithStaticSecret: legacy-api-scheduler
gcloud functions deploy legacy-api-scheduler \
  --entry-point CloudFunctionForSchedulerWithStaticSecret --trigger-topic project-legacy-scheduler \
  --region asia-southeast1 --runtime go124 --memory 128Mi --timeout 15s --gen2 \
  --update-labels service=legacy --max-instances 10 \
  --set-secrets DB_PASSWORD=db_password:latest,STATIC_SECRET=static_secret:latest,ENCRYPTION_KEY=encryption_key:latest,MAILJET_API_KEY=mailjet_api_key:latest,MAILJET_SECRET_KEY=mailjet_secret_key:latest \
  --env-vars-file .env-prod-cloud-function.yaml

Technical Architecture

System Architecture

graph TB
    subgraph CLIENT ["📱 Client"]
        WEB[Frontend<br/>sejiwo.com]
    end
    
    subgraph GATEWAY ["🌐 API Gateway"]
        LB[Load Balancer]
        MAIN[HTTP Server<br/>:8080]
    end
    
    subgraph API ["🔌 Endpoints"]
        API1["/legacy-api<br/>JWT Auth"]
        API2["/legacy-api-secret<br/>User Secret"]
        API3["/legacy-api-scheduler<br/>Static Secret"]
    end
    
    subgraph LOGIC ["⚡ Business Logic"]
        FRONTEND[Frontend APIs]
        SCHEDULER[Scheduler APIs]
    end
    
    subgraph DATA ["💾 Data Layer"]
        DB[(PostgreSQL<br/>Database)]
        CACHE[Connection<br/>Pool]
    end
    
    subgraph EXTERNAL ["🔗 External Services"]
        MAILJET[Email<br/>Service]
        SECRETS[Secret<br/>Manager]
        PUBSUB[Message<br/>Queue]
    end
    
    subgraph SECURITY ["🔒 Security"]
        ENC[AES<br/>Encryption]
        JWT[JWT<br/>Verifier]
        SEC[Secret<br/>Generator]
    end
    
    subgraph CRON ["⏰ Automation"]
        CRON1[Daily Reminders<br/>19:22]
        CRON2[Send Testaments<br/>19:38]
    end
    
    %% Primary Flow
    WEB --> LB
    LB --> MAIN
    MAIN --> API1 & API2 & API3
    
    API1 & API2 --> FRONTEND
    API3 --> SCHEDULER
    
    FRONTEND & SCHEDULER --> DB
    FRONTEND & SCHEDULER --> ENC
    
    %% External Connections
    DB -.-> CACHE
    FRONTEND & SCHEDULER --> MAILJET
    ENC & MAILJET & DB --> SECRETS
    
    %% Authentication
    API1 --> JWT
    JWT -.-> WEB
    
    %% Scheduling
    CRON1 & CRON2 --> PUBSUB
    PUBSUB --> API3
    
    %% Modern Styling
    style CLIENT fill:#1e293b,stroke:#334155,stroke-width:2px,color:#f1f5f9
    style GATEWAY fill:#0f172a,stroke:#334155,stroke-width:2px,color:#f1f5f9
    style API fill:#164e63,stroke:#0891b2,stroke-width:2px,color:#f0f9ff
    style LOGIC fill:#3730a3,stroke:#4f46e5,stroke-width:2px,color:#f0f9ff
    style DATA fill:#7c2d12,stroke:#ea580c,stroke-width:2px,color:#fef7ed
    style EXTERNAL fill:#166534,stroke:#16a34a,stroke-width:2px,color:#f0fdf4
    style SECURITY fill:#991b1b,stroke:#dc2626,stroke-width:2px,color:#fef2f2
    style CRON fill:#6b21a8,stroke:#9333ea,stroke-width:2px,color:#faf5ff

Database Schema

erDiagram
    EMAILS {
        varchar email PK "Primary identifier"
        timestamp created_at "Registration time"
        boolean is_active "Account status"
    }
    
    MESSAGES {
        uuid id PK "Message identifier"
        varchar email_creator FK "Message author"
        timestamp created_at "Creation time"
        varchar content_encrypted "Encrypted content"
        integer inactive_period_days "Delivery delay"
        integer reminder_interval_days "Reminder frequency"
        boolean is_active "Message status"
        char extension_secret "Extension token"
        date inactive_at "Delivery date"
        date next_reminder_at "Next reminder"
        integer sent_counter "Delivery attempts"
    }
    
    RECEIVERS {
        uuid message_id FK "Message reference"
        varchar email_receiver FK "Recipient email"
        boolean is_unsubscribed "Subscription status"
        char unsubscribe_secret "Unsubscribe token"
    }
    
    EMAILS ||--o{ MESSAGES : creates
    EMAILS ||--o{ RECEIVERS : receives
    MESSAGES ||--o{ RECEIVERS : "sent to"

Key Technical Features:

🏗️ Architecture: Go HTTP server on Google Cloud Run
🔐 Security: AES encryption, JWT authentication, secret management
📊 Database: PostgreSQL with optimized indexes for queries
📧 Email: Mailjet integration with HTML templates
⏰ Scheduling: Google Cloud Scheduler + Pub/Sub
🔄 Scalability: Stateless design, connection pooling
📈 Monitoring: Structured logging and error handling
🛡️ Reliability: Transaction-based operations, retry logic

Name		Name	Last commit message	Last commit date
Latest commit History 46 Commits
.vscode		.vscode
api		api
cmd		cmd
data		data
mail		mail
secure		secure
simple		simple
.dockerignore		.dockerignore
.env-dev-template.yaml		.env-dev-template.yaml
.env-prod-cloud-function-template.yaml		.env-prod-cloud-function-template.yaml
.env-prod-template.yaml		.env-prod-template.yaml
.env-test-template.yaml		.env-test-template.yaml
.gcloudignore		.gcloudignore
.gitignore		.gitignore
Dockerfile		Dockerfile
README.md		README.md
cloudbuild.yaml		cloudbuild.yaml
function_for_frontend_with_netlify_jwt.go		function_for_frontend_with_netlify_jwt.go
function_for_frontend_with_user_secret.go		function_for_frontend_with_user_secret.go
function_for_scheduler_with_static_secret.go		function_for_scheduler_with_static_secret.go
go.mod		go.mod
go.sum		go.sum
init-db.sh		init-db.sh
init.sh		init.sh
sqlc.yaml		sqlc.yaml
thunder-collection_legacy-api.json		thunder-collection_legacy-api.json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Repository files navigation

legacy-api

How Sejiwo Works

Key Features:

Prerequisites

Development

Database setup

Testing

Running the app in localhost

API call examples

Deployment

Technical Architecture

System Architecture

Database Schema

Key Technical Features:

About

Uh oh!

Uh oh!

Languages

asendia/legacy-api

Folders and files

Latest commit

History

Repository files navigation

legacy-api

How Sejiwo Works

Key Features:

Prerequisites

Development

Database setup

Testing

Running the app in localhost

API call examples

Deployment

Technical Architecture

System Architecture

Database Schema

Key Technical Features:

About

Topics

Resources

Uh oh!

Stars

Watchers

Forks

Uh oh!

Languages