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
Copy file name to clipboardExpand all lines: README.md
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,6 +184,46 @@ Deploy a WordPress theme from a directory to a hosting server. This tool uploads
184
184
-`themePath`: Absolute or relative path to the theme directory containing all theme files (required)
185
185
-`activate`: Whether to activate the theme after deployment (default: false)
186
186
187
+
### hosting_deployJsApplication
188
+
189
+
Deploy a JavaScript application from an archive file to a hosting server. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory; also exclude all files matched by .gitignore if the ignore file exists. The build process will be triggered automatically on the server after the archive is uploaded. After deployment, use the hosting_listJsDeployments tool to check deployment status and track build progress.
190
+
191
+
-**Method**: ``
192
+
-**Path**: ``
193
+
194
+
**Parameters**:
195
+
196
+
-`domain`: Domain name associated with the hosting account (e.g., example.com) (required)
197
+
-`archivePath`: Absolute or relative path to the application archive file. Supported formats: zip, tar, tar.gz, tgz, 7z, gz, gzip. If user provides directory path, create archive from it before proceeding. IMPORTANT: the archive must ONLY contain application source files, not the build output, skip node_modules directory. (required)
198
+
-`removeArchive`: Whether to remove the archive file after successful deployment (default: false)
199
+
200
+
### hosting_listJsDeployments
201
+
202
+
List javascript application deployments for checking their status. Use this tool when customer asks for the status of the deployment. This tool retrieves a paginated list of Node.js application deployments for a domain with optional filtering by deployment states.
203
+
204
+
-**Method**: ``
205
+
-**Path**: ``
206
+
207
+
**Parameters**:
208
+
209
+
-`domain`: Domain name associated with the hosting account (e.g., example.com) (required)
210
+
-`page`: Page number for pagination (optional)
211
+
-`perPage`: Number of items per page (optional)
212
+
-`states`: Filter by deployment states (optional). Valid values: pending, completed, running, failed
213
+
214
+
### hosting_showJsDeploymentLogs
215
+
216
+
Retrieve logs for a specified JavaScript application deployment for debugging purposes in case of failure.
217
+
218
+
-**Method**: ``
219
+
-**Path**: ``
220
+
221
+
**Parameters**:
222
+
223
+
-`domain`: Domain name associated with the hosting account (e.g., example.com) (required)
224
+
-`fromLine`: Line from which to retrieve logs (optional, default 0)
225
+
-`buildUuid`: UUID of the JavaScript deployment build (required)
0 commit comments