UNPKG

shipdeck

Version:

Ship MVPs in 48 hours. Fix bugs in 30 seconds. The command deck for developers who ship.

shipdeck.ai

shipdeckai/shipdeck

93 lines (70 loc) • 2.49 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
# Task 007: Deployment Automation Pipeline ## 1. Task Overview ### Task Title **Title:** Build automated deployment to Vercel, Railway, and Supabase ### Goal Statement **Goal:** Create seamless deployment automation that takes generated code from completion to live production URL without manual intervention, supporting multiple platforms. --- ## 2. Strategic Analysis ### Problem Context The 48-hour guarantee includes deployment. We need automated pipelines for different platforms (Vercel for frontend, Railway for backend, Supabase for database). ### Recommendation Build platform-agnostic deployment system with adapters for each service, including DNS and SSL setup. --- ## 3. Technical Requirements ### Functional Requirements - Auto-detect project type and choose platform - Create and configure projects on platforms - Handle environment variables securely - Set up custom domains - Configure SSL certificates - Database provisioning and migrations - Provide deployment URLs and credentials ### Non-Functional Requirements - **Speed:** Deploy in <5 minutes - **Reliability:** Retry failed deployments - **Security:** Never expose secrets - **Flexibility:** Support multiple platforms --- ## 4. Implementation Plan ### Phase 1: Vercel Integration - [ ] Integrate Vercel API - [ ] Implement project creation - [ ] Add environment variable management - [ ] Configure build settings - [ ] Handle custom domains ### Phase 2: Railway Integration - [ ] Integrate Railway API - [ ] Set up service deployment - [ ] Configure database connections - [ ] Handle environment sync - [ ] Manage scaling settings ### Phase 3: Supabase Integration - [ ] Integrate Supabase Management API - [ ] Provision new projects - [ ] Run database migrations - [ ] Set up authentication - [ ] Configure Row Level Security ### Phase 4: Orchestration Layer - [ ] Create deployment decision engine - [ ] Build rollback mechanisms - [ ] Add health checking - [ ] Implement monitoring setup - [ ] Create deployment reports --- ## 5. Success Criteria - [ ] Can deploy Next.js app to Vercel - [ ] Can deploy Node.js API to Railway - [ ] Can provision Supabase database - [ ] Environment variables sync correctly - [ ] Custom domains work with SSL - [ ] Rollback works on failure --- ## 6. Dependencies - Platform API keys (Vercel, Railway, Supabase) - Task 003 (Vertical Slice) for testing --- ## 7. Estimated Effort **Priority:** P0 (Critical - Week 3) **Complexity:** High **Duration:** 5 days