← All posts

One SSH Command, One Click, and Your WordPress Site Is Live

November 2, 2026 · 4 min read · The xShellz Team

TL;DR

  • One click installs WordPress or Ghost on a 24/7 Ubuntu 24.04 Agent Shell box, serving on port 8080.
  • Publishing turns the app into a frozen, malware-scanned static copy that goes live at https://.turborg.com.
  • The box has no trial countdown and no idle shutdown, so the site keeps serving after you close your terminal.

Spin up a live WordPress site from your terminal by SSHing into an xShellz Agent Shell box, clicking WordPress in the one-click app list, and publishing the result. The site first serves on port 8080 inside the box, then goes live at https://.turborg.com as a frozen, malware-scanned static copy. We run the xShellz fleet ourselves: the borg terminal agent, the Agent Shell boxes and the hosted model gateway, and this one-click install path is the setup we use for our own throwaway sites.

how do i quickly spin up a live wordpress site from my terminal?

The short path: connect to the box with one SSH command, pick WordPress from the one-click apps, and publish. No domain, no DNS, no separate database server to configure. The box runs Ubuntu 24.04 LTS, you log in as root, and /root is your persistent home.

ssh -p <port> root@<host>

That single SSH command drops you into the shell. From there the WordPress install is one click in the box's web terminal, which you can open in any browser with no key. WordPress needs PHP and a database, and the one-click install handles both without you touching a config file.

how do i install a cms like wordpress or ghost on a remote shell

The answer is one click, not a package command. WordPress and Ghost are two of the 23 one-click apps on every Agent Shell box. You do not run an installer, edit a config file, or set up a database by hand. Choose the app in the box's web terminal, click install, and it serves on port 8080. Ghost gets the same treatment as WordPress. If you prefer to script your environment, the xshellz.box manifest in your home directory reinstalls packages on every boot, but the CMS apps themselves are the one-click path.

how to publish a website live from a linux sandbox

Publishing is a separate step from installing. The app serves on port 8080 inside the box, but that is not yet public. To go live, you publish the app, which freezes it into a static copy, scans it for malware, and serves it at https://.turborg.com. That two-step design is deliberate: the live site is a frozen snapshot, so changes to the running CMS do not reach visitors until you publish again. The box keeps running, but the published site is what your visitors hit. Static site apps in the one-click list, like Hugo or Jekyll, publish the same way.

can i host a ghost blog on a throwaway xshellz box

Yes, and a throwaway box is a good fit for a Ghost prototype. Every box includes Ghost in the 23 one-click apps. You can spin up a box, install Ghost, write a few posts, publish it live at https://.turborg.com, and decide whether to keep it. Stopped boxes are kept for 30 days before cleanup, so a throwaway box does not vanish the moment you stop using it. If the blog earns a permanent home, keep your durable content under /root, which is the persistent home and the only path that survives a rebuild.

what is the fastest way to deploy a static site or cms for testing

For testing, the one-click list on an xShellz box beats a local dev server because there is nothing to install on your side. 23 apps are one click away: WordPress, Ghost, Drupal, Statamic, Directus, Strapi, Grav, MkDocs, Hugo, Eleventy, Astro, Next.js, Nuxt, VitePress, Docusaurus, Hexo, Jekyll, Zola and more. Compare that to a laptop setup: install PHP or Node, pull the CMS, configure a database, get it listening. On the box, the app serves on port 8080 after the click, with no dependency install step for you. And because every tier is always-on with 0 idle timeout, the test site is still there tomorrow.

Frequently asked questions

Do I need my own domain to publish a WordPress site?

No. The published site lives at https://.turborg.com, so your xShellz account name is the domain. You do not buy a domain, configure DNS, or manage SSL certificates. The box serves the app on port 8080 internally, and publish maps it to that public URL.

Does my WordPress site keep running after I close my laptop?

Yes. Every xShellz Agent Shell box, including the free tier, runs 24/7 with 0 idle timeout and 0 trial countdown. Closing your terminal or shutting your laptop does not stop the box, the CMS, or the published site. A site that only lives while your terminal is open is a demo, not a deployment.

What is the difference between the app on port 8080 and the published site?

Port 8080 is the live CMS inside the box, where you log in, write posts and make changes. The published site is a separate, frozen static copy that visitors reach at https://.turborg.com. It is malware-scanned at publish time. Changes to the running CMS do not reach the public site until you publish again.