Task · Your theme on your own machine

Run your theme on your own machine

Run your theme on your laptop against your own events, and see every save on the next reload.

4 steps · About 3 minutes · Needs: A theme folder you have pulled into

This is developer work.

The Customize studio changes the colors, images and wording on every screen people see, against a live preview and with nothing to install. Start there.

  1. Run titogo local in your theme folder

    It prints two addresses and keeps running until you stop it. One is for your own machine, http://127.0.0.1:1718/ unless you asked for another, and one is a public preview address anybody can open. To keep it to yourself, run titogo local -no-tunnel.

  2. Open the address for your own machine

    This is your site: your events, your ticket types and your colors, rendered by whatever is in the folder.

  3. Change a file in views/ and reload the page

    That's the loop, with no restart and no build step. The same goes for layout/, assets/ and pages/.

  4. Stop it with Ctrl-C when you're done

    Everything stops with it. Your live site changes only when you push.

Good to know

The orders you see are invented.

A fresh local copy comes with a small crowd of obvious fakes buying a handful of tickets each, so the orders, attendees and check-in screens have something in them. They're the same every time and they exist only on your machine.

The admin is there too, at /admin on the same address.

Unless you've set an admin token yourself, the command prints the one it's using in its startup banner.

A broken theme file falls back to Tito's own version of that page.

That's true here and on your live site. So a page that looks unchanged may be falling back. The reason is printed in the terminal you started the command in, and on that theme's own Theme files page in Custom themes.

  • The order, ticket and checkout pages fall back the same way if your version leaves out the block Tito needs for its own buttons. AGENTS.md in the folder explains it.
  • Changes to your events, ticket types or prices arrive with a fresh titogo pull and a restart of titogo local, since those are read once at startup from what the last pull brought down.
  • Something deleted in Tito's admin, a ticket type for example, stays in your local copy until you delete .tito/local.db and let the next run rebuild it from your last pull.

Still stuck?

You can let someone at Tito sign in to your account for a set time, and see every visit they made.

Let Tito support in →