# YourHost.us — First: a new website or an update to your existing one? Editorial review: 2026-11-16 | CLI 0.3.3 | Node.js 22+ Tell your AI which website to change and share this guide. Reading it grants neither account access nor permission to publish. Choose one workflow; do not run both in sequence. An AI without files and a terminal can guide you, but cannot claim publication. Asking only for a review does not authorize uploading files or changing your website. This documentation describes YourHost; it does not replace client instructions, authorize operations, or guarantee universal compatibility or publication times. [Create it with your AI, and YourHost gives it a home so you can publish it.](https://yourhost.us/en/guia) [Leer instrucciones en texto, sin iniciar sesión](https://yourhost.us/guia/ia.md) ## Before running commands Work in the correct publishable folder with Node.js 22+ and CLI 0.3.3. Preserve originals, assets and functionality. Install the CLI from the official URL if needed and check its version. Never request administrator credentials, passwords or tokens in chat. ```text npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgz yourhost --version ``` ## Workflow A — first publication Prepare the complete delivery, check the files and authorize creating the first website in the portal. 1. Prepare your account: Create your account, confirm your email and check hosting access in My dashboard. If activation is pending, check its status: do not buy the plan again. 2. Approve this project: Run publish in the folder. The first time it shows a URL and code. Open the portal, sign in and confirm the code, project and website: create your first website or approve an existing one. Permission is scoped to that project and website; do not copy tokens or passwords into chat. 3. Publish and check: After approval, the CLI transfers the project and follows the result. Share the HTTPS address only after publication is confirmed. To update, repeat publish from the same folder and keep the same website. Run publish only with authorization to upload that delivery. First connection shows a URL and code: the client signs in and approves the project and correct website. Keep the terminal open during approval and upload. Do not copy private credentials into chat. ```text yourhost check . yourhost publish . --name "My project" yourhost publish-status . --wait ``` ## Workflow B — update the same website Identify its address and keep that same website. When connecting another folder for the first time, approve the existing website: do not create a duplicate. publish and ZIP need a complete delivery of the updated project, not only changed files. Omitted source files are removed from the new version. Preserve required assets and functionality; prepare a publishable copy without secrets, without deleting originals. The advanced delta has a different contract. If this folder already has a saved submission, check its status before publishing changes. A never-connected folder cannot automatically discover a website created with ZIP: identify the website in My websites and approve that existing website when connecting. Keep the same folder and local website connection (binding). --name is for first creation, not renaming a connected project. Do not delete receipts, snapshots or locks to force publication. ```text yourhost check . yourhost publish . ``` Signing in does not replace hosting or website permission, or remove quotas and validation. For a new rejection, keep its code and UUID and ask support; do not create another website or buy another plan to bypass it. Never send passwords or tokens. A website with data or a special persistent profile has its own procedure. Do not recreate it, switch runtime or assume delta eligibility. Preserve data and check compatibility. ## Checking is not publishing publish-status makes GET requests for the saved submission; it may update local receipts and locks, but creates no remote publication. It does not automatically discover support repairs or the global website status. yourhost publish-status . queries the last submission saved by the CLI in that folder. It does not publish your changes or automatically discover a later repair made by support. failed or published=false describe that submission; they do not prove that the website is down or your account is blocked. Compare identifiers with My websites and the version at your HTTPS address. ```text yourhost publish-status . --wait ``` In the CLI, wait for “Publicación HTTPS confirmada: …” (HTTPS publication confirmed); in the portal, Online. The CLI checks jobStatus=succeeded and published=true in the API before showing that confirmation, but does not necessarily print those JSON fields. Then open HTTPS and check your content. A reserved URL, received archive or exit code 0 with --no-wait is not enough. Duration varies: there is no guaranteed publication time (SLA). ## When the outcome is unclear ### Different sources and a finished previous submission Use normal publish, without --retry or --reconnect. Keep the folder and website: a new UUID is created for that version. After confirmed success, open HTTPS and check the content. ### Pending submission or uncertain result Query yourhost publish-status .; add --wait to follow it. Resuming publish preserves snapshot and UUID even if you edited files. It does not create the new version yet. Do not delete locks or receipts to force another submission. ### Repeat exactly the failed content --retry is only for a confirmed transient failure. PUBLICATION_FAILED without a specific cause needs support before repeating that content; keep requestId, uploadId and attemptId. Received files do not mean publication. ### Expired or revoked permission --reconnect requires a confirmed terminal result and approval of the same website. It renews access, not publication. Do not use it to resolve an old failed result with a valid credential. CLI 0.3.3 and the JavaScript portal transfer blocks of up to 1 MiB. Query without publishing using yourhost publish-status .: it only makes GET requests for the submission saved in that folder; add --wait to follow it. It does not automatically query a later repair made by support. While a submission is pending, repeat yourhost publish . in the same folder: it recovers snapshot and UUID even if sources changed. After a confirmed terminal result, identical sources only check status; different sources create an update for the same website using normal publish, including when the previous result was failed. Do not use --retry to incorporate changes. yourhost publish . --retry is reserved for a confirmed transient failure and identical content; it requires confirmed failed, complete transfer and published other than true. It creates a new UUID: it is not a query or a format correction. For PUBLICATION_FAILED without a specific cause, consult support before repeating that content. yourhost publish . --reconnect only renews expired/revoked access with a confirmed terminal result and approval of the same website; it does not publish changes or resolve uncertainty. Combine --reconnect --retry only when both conditions hold. Use yourhost publish . --recover-lock only if the CLI verifies that the recorded process ID (PID) no longer exists. Legacy locks without the new process metadata are not removed automatically. Never delete receipts to start another submission. If the portal closes before transfer completes, return with the same file. Only durable server acceptance lets work continue without the window. --no-wait is an alternative that skips waiting for the build: it waits for approval and upload; do not run it as a second submission. A wait ending confirms neither failure nor publication. ## Formats and limits: the channel matters too check inspects local files: it does not authenticate, upload or run scripts and does not guarantee server compatibility or admission. CLI 0.3.3 check/publish accepts up to 2048 files in its folder, even though some portal ZIP formats accept 4096. check uses the normal 20 MiB ZIP limit; publish negotiates the normal 20 MiB or up to 128 MiB with Owner permission, without expanding format limits or quotas. HTML accepts local MP4/WebM and up to 10 MiB per file. HTML, Node.js/Next.js, Vite and WordPress backups require compatibility. Generic DB, SMTP, secrets, persistence and egress are not available. Exclude .env files (including examples), keys, wp-config.php and pb_data from the publishable copy; preserve originals. SOURCE_UNSUPPORTED calls for reviewing the delivery, not blindly converting it. Do not remove package.json, lockfiles, backend code or requirements to force HTML, or replace an application with a mockup. A static export is appropriate only if it actually exists, preserves the agreed functionality and you authorize that change. ### HTML The ZIP can be up to 20 MiB: 50 MiB extracted, 512 files and 10 MiB per file. Local MP4/WebM videos are supported, without server transcoding. Zip the website contents, not an outer folder. An already compiled dist/ export also uses this workflow. A ZIP containing your files is required; the form does not generate an example page. Prepare my website for YourHost as static HTML. Deliver a ZIP with index.html at the root, CSS, JavaScript, local images and MP4/WebM videos using correct paths. Maximum 20 MiB ZIP, 50 MiB extracted, 512 files and 10 MiB per file. Exclude hidden files, secrets, node_modules and Docker files. Do not publish without my authorization. ### Next.js / Node.js The start script must listen on 0.0.0.0:3000; add build when needed. The platform prepares npm dependencies. Build code cannot download Internet resources. This profile has no configurable secrets. Ask about compatibility before uploading if you need a DB, persistence or server-side access to an external API. This profile has no DB, persistent disk or outgoing server network. Prepare my Next.js or Node.js project for YourHost. Include package.json, npm package-lock.json and start on 0.0.0.0:3000; build if needed. Use pinned registry.npmjs.org dependencies and local assets. No downloads during build. This profile has no DB, persistence, configurable secrets or outgoing server network. Explain incompatibilities before delivery. Maximum 20 MiB ZIP; source 50 MiB/4096 files/20 MiB per file. Exclude hidden files, .env, node_modules and Docker. Do not publish without permission. ### Vite / React Vite source needs build, not start. We publish only validated dist/ output. For a compiled export, place index.html at the ZIP root for automatic HTML detection. Browser calls to external services differ from server connections: check CORS and never expose secrets in the frontend. Already have compiled dist/? Upload its contents as HTML. Prepare my Vite project for YourHost with package.json, package-lock.json and build producing dist/. Include local assets; no downloads during build. Maximum 20 MiB ZIP; source 50 MiB/4096 files/20 MiB per file. The dist output needs index.html, maximum 50 MiB/512 files/10 MiB per file. Exclude secrets, hidden files, node_modules and Docker. For compiled dist delivered as HTML, put index.html at the ZIP root. Do not publish without permission. ### WordPress Use database.sql and wp-content/ containing media, plugins or themes. An imported backup keeps its users and passwords. A new import does not merge live edits: it creates a new generation and preserves the current one until validation. This form does not create empty WordPress sites. Always keep your original backup. Plugins must be compatible: PHP has no outgoing network or online updates. Prepare a YourHost-compatible backup: database.sql at the root and wp-content/uploads, plugins and themes as applicable. Maximum 20 MiB ZIP, source 50 MiB/4096 files/20 MiB per file. Exclude wp-config.php, infrastructure secrets and hidden files. Check plugins/themes: this profile has no outgoing PHP network or online installation/updates. Do not run SQL or publish without my authorization. ## Other channels, not additional steps ZIP, Git, SFTP and API are alternatives with their own permissions. Do not chain them to publish twice. deploy packages static HTML only; it is not a universal replacement for publish. ### Git Publish by pushing to main. 1. Add your Ed25519 public key (.pub) under Git and SFTP upload. 2. Copy the portal URL and place files in public/ (HTML) or source/ (projects/WP). 3. Push to main and check the same website's status. Keep your private key on your computer; the portal receives only the public key. Access lasts 90 days and can be revoked. There is no shell. Other branches, force-push and deleting main are rejected. Verify the host fingerprint shown in the portal. ### SFTP Upload with FileZilla or WinSCP. 1. Configure your public key on the website and copy its SFTP username. 2. Connect over SFTP to portal.yourhost.us:7387 with your local private key. 3. Upload public/ or source/ under /upload and select Publish SFTP staging in the portal. Uploading does not publish immediately: files first enter staging. Publish SFTP staging validates and submits the version. Use SFTP, not unencrypted FTP or your portal password instead of a key. You can access only the authorized website. ### CLI publish connects your project; support sends reviewed requests; deploy and source keep their advanced contracts. 1. Install CLI 0.3.3 with Node.js 22 or later. Use check to review and publish from the project folder. 2. Approve the URL and code in the portal, without copying tokens. Keep the terminal open during authorization and transfer; follow the same submission to its result. 3. deploy/source use YOURHOST_SITE_TOKEN; support also accepts the connected project private credential, but an environment token takes priority. source depends on website eligibility returned by the server; the cloudpage-pocketbase-v1 persistent example requires Owner. Continue only with eligible: true and use the plan id. publish uses project permission approved in the portal; it does not need YOURHOST_SITE_TOKEN. publish-status only queries an existing submission. deploy packages static HTML: ZIP 20 MiB and 10 MiB per file. source is an advanced delta, not an installer or runtime change: the server confirms eligibility and current permission. The persistent example in this guide requires Owner and cloudpage-pocketbase-v1 binding; do not generalize it to all applications. Repeat --files for existing files under src/, messages/ or public/. Maximum 1 MiB/128 files; omitted files preserved, plans and snapshots retained 24 hours. Use plan id, not requestId. Only attempt.status: succeeded and published: true confirm publication. PocketBase data, hooks/schema, configuration and dependencies are separate. The site key expires in 90 days and is revocable. Keep .yourhost/ private and outside Git: source receipts contain sources. publish keeps snapshot and credential outside the project. ### API Automate a ZIP with a website key. 1. Open Manage your website and create a publishing key. 2. Send the ZIP with Bearer authorization and a UUID in Idempotency-Key. 3. If the response is lost, keep the same UUID and ZIP; check status before sending again. Use only that website's key and authorize each publication. Permissions, project type and limits also apply. Revocation prevents new operations; an already accepted publication may finish. The dedicated MCP integration is not available. ### Advanced: update an eligible source delta. The advanced example in this guide concerns an active website with the cloudpage-pocketbase-v1 persistent profile, which requires Owner authorization and an available binding. The server determines eligibility for each website: continue only with eligible: true. Do not infer access from using Next.js, Node.js or Vite. Persistent data and configuration have their own procedure. Up to 1 MiB and 128 files per change, under src/, messages/ or public/. The plan and its file snapshot expire after 24 hours. Omitted files are preserved. This channel does not install a new application or change dependencies, private configuration, databases or PocketBase hooks/schema. 1. Save and review your changes: Open a terminal in your project folder. Check that the local version works and choose the files to update. 2. Prepare a plan: The command compares your files with the remote version and saves changes in a plan. It does not publish yet. Replace the example path with one that exists in your project; repeat --files to add more files. ```text yourhost source plan . --files src/app/page.tsx ``` 3. Find the plan code: Look for the id field in the response. This is the code used to publish and check the result. The requestId field identifies the submission; do not use it as the plan code. 4. Publish and check: Replace PLAN_ID with the real id value. When publication finishes, open the same website address and review the pages you changed. ```text yourhost source apply PLAN_ID --wait ``` The codes shown here are examples. Copy the real id value from your own response, without quotation marks. attempt.status: succeeded and published: true mean the attempt finished and is the published version. ready means the plan is prepared; queued or building mean work is still in progress. An accepted publication can continue after you close the terminal. Check the same plan; if the response asks you to resume, use resume with that same code. Do not create another publication just to find out what happened. ```text yourhost source status PLAN_ID yourhost source resume PLAN_ID --wait ``` unchanged means the selected files already match the remote version. No extra publication is created. If a plan expired, check its status first, then prepare a new one with your current changes. [Advanced: update an eligible source delta.](https://yourhost.us/en/guia#autoservicio) ## Ask for support from your project with your AI. Your AI with files and a terminal can submit a request to support@yourhost.us using CLI 0.3.3 and Node.js 22 or later. Creating SMTP-INTEGRATION.md on your computer sends nothing. 1. Prepare and review the request: Describe the issue, expected result and reproduction steps in SMTP-INTEGRATION.md. Do not include passwords, tokens, keys or other secrets. Review the content and explicitly authorize submission. 2. Send one identifiable request: If YOURHOST_SITE_TOKEN is set, it takes priority over privateStore; --folder does not override that token. Without that variable, the CLI uses the bound folder's private credential (privateStore); use --folder when working elsewhere. Verify that access belongs to the correct website; the server validates the binding. Generate one real UUID and save it with the exact subject and file before submission; replace , do not run it literally. 3. Save the ticket and check its status: The response returns the ticket UUID with status: received before sending the SMTP notification. Save that ticket and replace to check it. support list shows up to your website's 50 most recent requests without resending them. The request UUID is not the ticket UUID. If YOURHOST_SITE_TOKEN is set, it takes priority over privateStore; --folder does not override that token. Without that variable, the CLI uses the bound folder's private credential (privateStore); use --folder when working elsewhere. Verify that access belongs to the correct website; the server validates the binding. Keep the token private, without displaying it or sharing it in chat; never print its value. To use privateStore you may unset the variable only in your own safe environment, with your authorization; do not delete local credentials. You do not need administrator access and must not add credentials to the support file. ```text node -e "console.log(crypto.randomUUID())" ``` ```text yourhost support submit SMTP-INTEGRATION.md --subject "Contact form" --request-id ``` ```text yourhost support status yourhost support list ``` received confirms durable ticket receipt, not resolution or email delivery. A request is not automatically executed and does not enable generic SMTP, egress, secrets or configuration for your website. notificationState describes the email notification: queued (waiting), retry (safe retry), sending, sent (accepted by SMTP), failed or uncertain. sent proves neither inbox delivery nor reading. uncertain needs review: do not blindly resend. If the response is lost, keep the same request UUID, subject and exact file for replay; check support list and the ticket if known. Do not generate a new UUID to resolve uncertainty. Changing content with the same UUID is not a replay. An empty list does not prove the local MD was submitted: check the bound folder or --folder and query the real ticket UUID if already received; do not reconnect or create another ticket to force it to appear. Maximum: 12,000 message characters, 20 KiB JSON body and 160 subject characters. Up to 20 new requests in the last 24 hours and 200 retained per account; an identical replay does not create another ticket. These limits do not permit secrets. ## Connect your own domain. With a paid plan: up to five domains per website. Enter the name without https:// or a path. Add the root domain and www separately. Copy real values from your dashboard; diagrams are examples. Keep your email provider and its MX records. HTTPS is prepared once ownership and destination DNS are verified. [Connect your own domain.](https://yourhost.us/en/guia#dominios) ## Mail and external resources Available now: a read-only view of associated domains and mailboxes. Automated purchasing and provisioning of standalone email are still pending; no prices or immediate activation are offered here. Unified webmail sign-in is also pending. Select Open webmail in the email view. An external site opens: sign in with your email address and mailbox password. Your portal session does not sign you in there automatically. ## Copyable client instructions ### Publish Publish this project on YourHost with CLI 0.3.3 and Node.js 22+. 1. Check that you have files and a terminal. Without them, guide me without claiming publication. 2. Establish whether I want a new website or an update. If it already exists, identify its URL and select that same website during approval; do not create another. 3. Prepare a complete delivery of the updated project without secrets, preserving originals and functionality. Do not supply only changed files. Do not remove package.json, lockfiles or backend code to force HTML after SOURCE_UNSUPPORTED. 4. Run yourhost check . and explain incompatibilities. check does not guarantee server admission. 5. With my authorization, run yourhost publish . once. When connection is needed, show the URL and code for me to approve the project and website in the portal. Never display tokens or passwords. 6. Keep the folder, binding, valid credential, website and receipts. Keep the terminal open during approval and upload. 7. Query the saved submission using yourhost publish-status . --wait. While pending, publish . resumes its snapshot and UUID even if sources changed; it does not yet publish the new version. 8. After a confirmed terminal result, authorized new sources use normal publish, without --retry or --reconnect. A historical failed does not prove my website is down. Do not resend identical content after an unknown failure. 9. Wait for the actual CLI message: Publicación HTTPS confirmada. The API requires jobStatus=succeeded and published=true, but the CLI does not necessarily print that JSON. Then check my content over HTTPS. ### Update Update my existing YourHost website with CLI 0.3.3 and Node.js 22+. 1. Identify its URL and bound publishable folder; do not recreate the website or delete receipts, snapshots or locks. Without files or a terminal, guide me without claiming execution. 2. Preserve a complete delivery of the updated project, including assets and unchanged files. publish is not a delta: omitted source files are removed from the new version. Preserve originals and functionality; do not remove manifests or backend code to force HTML. 3. If a saved submission exists, query yourhost publish-status . --wait and keep its identifiers. A historical failed is not the global website status: compare My websites and any support repair. 4. If pending or uncertain, query or resume its snapshot and UUID; new edits wait until it finishes. Do not force another submission. 5. With a confirmed terminal result and different sources, run yourhost check .; review changes with me and wait for authorization for normal yourhost publish . Preserve binding, website and valid credential; no --retry or --reconnect for new files. 6. If this folder has never been connected, approve the existing website in the portal rather than create another. Do not use --name to rename a connected project. 7. Do not repeat identical content after PUBLICATION_FAILED without support diagnosis. Review SOURCE_UNSUPPORTED without destructively converting the application. 8. Wait for Publicación HTTPS confirmada in the CLI; jobStatus=succeeded and published=true belong to the API contract. Then check the content over HTTPS. Never display or request secrets in chat.