Hostinger OpenClaw VPS
deploy_files
NEW SITE? STOP — run the BUILD ORDER first (get_account → ask single-file vs multi-page + notification emails → create_data_collection for EVERY repeating section → create_form / create_booking_page → upload_media → THEN deploy). Deploys a multi-file site from inline file contents (HTML, CSS, JS; index.html at the root required). Compose every file DIRECTLY in this call — never stage to your filesystem first. Data sections use the declarative data-dp-collection markup; hardcoded list content is a BROKEN build. After deploy: assign_to_project, configure_chatbot, and ALWAYS hand the user the complete site code in your own interface — deploying alone is not the deliverable. get_guide("workflow") has the full rules. Returns a live URL; reusing a project name redeploys it in-place.
Remote (network-hosted)
Other tools also called deploy_files?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "URL-friendly project name (e.g. 'my-landing-page'). If omitted, a name is generated. Reusing an existing name will redeploy."
},
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"path",
"content"
],
"properties": {
"path": {
"type": "string",
"description": "Relative path inside the site, e.g. 'index.html', 'css/style.css', 'about.html'"
},
"content": {
"type": "string",
"description": "The full text content of the file"
}
}
},
"description": "Every file of the website. Must include index.html at the root. Text files only — reference images by their upload_media URLs instead of bundling them."
}
}
}