You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "Automatically deploys the SDK app to the router after Kiro finishes making code changes. Uses make.py deploy.",
5
+
"version": "1",
6
+
"when": {
7
+
"type": "agentStop"
8
+
},
9
+
"then": {
10
+
"type": "askAgent",
11
+
"prompt": "If you just created or modified any SDK app Python files during this session, deploy the app now by running: python3 make.py deploy {app_name} (substitute the actual app name). If no app code was changed, do nothing."
"description": "One-click deploy of the current SDK app to the router via deploy.sh. Verifies the app started successfully by reviewing log timestamps.",
4
+
"description": "One-click deploy of the current SDK app to the router via make.py deploy. Verifies the app started successfully by reviewing log timestamps.",
5
5
"version": "1",
6
6
"when": {
7
7
"type": "userTriggered"
8
8
},
9
9
"then": {
10
10
"type": "askAgent",
11
-
"prompt": "Read sdk_settings.ini to get the app_name, then run: bash deploy.sh <app_name>. After the command completes, review the output for errors. Check that log timestamps are AFTER the deploy started. If logs show the app started successfully, report success briefly. If there are errors, diagnose and suggest fixes."
11
+
"prompt": "Read sdk_settings.ini to get the app_name, then run: python3 make.py deploy <app_name>. After the command completes, review the output for errors. Check that log timestamps are AFTER the deploy started. If logs show the app started successfully, report success briefly. If there are errors, diagnose and suggest fixes."
Copy file name to clipboardExpand all lines: .kiro/steering/workflow.md
+19-10Lines changed: 19 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,16 @@ Use `python3` for all commands.
24
24
-**When user says "learn"** - Load `.kiro/steering/learn.md` (Update rules and docs based on what was learned)
25
25
-**When user says "deploy"** - Load `.kiro/steering/deploy.md` (Deploy app to router workflow)
26
26
27
+
## Auto-Deploy
28
+
29
+
**ALWAYS deploy after creating or modifying an app.** After any code change to an app's Python files, automatically run:
30
+
31
+
```bash
32
+
python3 make.py deploy {app_name}
33
+
```
34
+
35
+
Do NOT ask the user if they want to deploy — just do it.
36
+
27
37
## Configuration Files
28
38
29
39
-**NEVER make up configuration formats** - always reference actual files like @sdk_settings.ini
@@ -80,27 +90,26 @@ This generates all required files from app_template (package.ini, start.sh, cp.p
80
90
81
91
**NEVER overwrite package.ini, start.sh, or cp.py after creation** - these are auto-generated and correct.
82
92
83
-
**ALWAYS deploy after creating or modifying an app** - use `bash deploy.sh {app_name}` immediately after code changes.
93
+
**ALWAYS deploy after creating or modifying an app** - use `python3 make.py deploy {app_name}` immediately after code changes.
84
94
85
95
## Deploy to Router
86
96
87
-
**ALWAYS use deploy.sh script** - `bash deploy.sh {app_name}`
97
+
**ALWAYS use make.py deploy** - `python3 make.py deploy {app_name}`
88
98
89
-
This script handles:
90
-
-Cleaning old build artifacts
99
+
This handles:
100
+
-Purging old apps
91
101
- Building the app package
92
-
- Stopping the old version
93
102
- Installing the new version
94
-
- Starting the app
103
+
- Starting the app (auto_start=true in package.ini)
95
104
- Showing status and logs
96
105
97
-
**Just run `bash deploy.sh {app_name}`** - no need to run `make.py clean` or remove old tar.gz files first. deploy.sh handles everything. The app auto-starts after install (auto_start=true in package.ini), so there's no need to run `make.py start` either.
106
+
**Just run `python3 make.py deploy {app_name}`** - no need to run `make.py clean` or remove old tar.gz files first. It handles everything. The app auto-starts after install, so there's no need to run `make.py start` either.
98
107
99
-
**NEVER use make.py install directly** - always use deploy.sh for deployment.
108
+
**NEVER use make.py install directly** - always use `make.py deploy` for deployment.
100
109
101
-
**deploy.sh output is sufficient** - if logs show app started successfully (e.g., "Starting app_name", "Web server started"), DO NOT run status or logs commands again. The deployment verification is already complete.
110
+
**deploy output is sufficient** - if logs show app started successfully (e.g., "Starting app_name", "Web server started"), DO NOT run status or logs commands again. The deployment verification is already complete.
102
111
103
-
**ALWAYS check log timestamps after deploy** - deploy.sh shows timestamps (HH:MM:SS) on each log line. Only trust logs with timestamps AFTER you ran the deploy. The router log buffer contains old entries from previous deploys — if you see logs without recent timestamps, they are stale and do not reflect the current deploy.
112
+
**ALWAYS check log timestamps after deploy** - deploy shows timestamps (HH:MM:SS) on each log line. Only trust logs with timestamps AFTER you ran the deploy. The router log buffer contains old entries from previous deploys — if you see logs without recent timestamps, they are stale and do not reflect the current deploy.
0 commit comments