Try Turborg Free → Open App →
← All posts

I Clicked a Button and Got a Live Blog. No Server Config, No YAML.

July 27, 2026 · 2 min read · The xShellz Team

You want a blog, but you don't want to become a part-time sysadmin. Normally that means picking a managed platform and giving up control. xShellz gives you the middle ground: a real Linux environment where you can install a full CMS with one click, then publish a fast, static copy of your site to the internet.

A box on xShellz is an always-on Ubuntu 24.04 sandbox that runs your apps. It comes with a dashboard that lets you install WordPress, Ghost, or static site generators like Hugo with a single click. The app runs on port 8080 inside the box, but you never expose it to the public. Instead, you set it up over an SSH tunnel, then click Publish to deploy a frozen, malware-scanned static copy to https://<your-username>.turborg.com.

One Click to a Running CMS

Here is the whole flow for Ghost:

  1. Log into your xShellz dashboard and create a new box (the free tier stays online forever).
  2. Find the Ghost one-click install button and click it. In about 30 seconds, Ghost is running on port 8080 inside the box.
  3. Open an SSH tunnel to your box so you can access Ghost from your local browser:
# Replace the host and port with the details from your dashboard
ssh -L 8080:localhost:8080 -p 2222 [email protected]

  1. Now visit http://localhost:8080/ghost in your browser and complete the setup wizard: create your admin account, set your site title, and write a first post.

  2. Once you are happy, head back to the dashboard and click Publish. The platform takes a snapshot of your Ghost output, scans it for malware, and pushes a static copy to your subdomain. Your site is live at https://yourusername.turborg.com.

That is it. No Apache config files, no database tuning, no Let's Encrypt renewal scripts. The static copy is served from a CDN, so it loads fast and has no moving parts to maintain.

What About WordPress?

The same flow works for WordPress. Click the WordPress icon, tunnel in, run the famous 5-minute install through your browser, and publish. The static copy includes all your pages and posts as flat HTML. Dynamic features like native comments or search will need a third-party service (Disqus, Algolia), but for a simple side project that is a fair trade for never having to update plugins or worry about a database.

When This Helps (and When It Doesn't)

This approach shines for side projects, documentation sites, and blogs where you want full control over the content but zero ops overhead. The box is your private staging area; the published static site is your live product. The limit is that you give up server-side dynamic behavior unless you wire up external APIs. If you need real-time user-specific data, you might still need a traditional host. But for the vast majority of personal and small-team sites, a static copy of a well-known CMS gets you 90% of the benefit with almost none of the work.