Services & tools

Public links

Share a local site at a public https:// address, with a password and a time limit.

Share a local site at a public https:// address: show a client your work, test on your phone over mobile data, or receive real webhooks from Stripe and GitHub. It's free, goes through a Cloudflare quick tunnel, and needs no account.

Sharing a site

  1. Open the site's Share tab

    Sites → click the site → Share.

  2. Choose who can open it

    Anyone with the link (the address is long and random, good for webhooks and quick demos) or Only with a password (browsers ask for a username and password first).

  3. Choose how long

    1 hour, 8 hours, 1 day, or until you stop it. The link closes by itself when the time is up.

  4. Start it

    A few seconds later you get an address like https://quiet-river-1234.trycloudflare.com, with Copy and Open buttons. The Share tab is marked live while the link works.

The first link downloads Cloudflare's small tunnel program (cloudflared) once; after that a link takes a few seconds.

From the terminal

$ cd ~/Code/shop
$ laramonster share
Opening a public link for shop…
✓ shop is public at https://quiet-river-1234.trycloudflare.com
Stop it with `laramonster unshare shop`.

# With a password, for two hours
$ laramonster share shop --user client --password 'demo-2026' --minutes 120

$ laramonster unshare shop

How Laravel sees it

Requests through the link reach your computer's copy of the site, with its database. LaraMonster tells Laravel the request came over HTTPS from the public address, so url(), route(), redirects, signed URLs and asset links all use the public address, with no change to APP_URL or TrustProxies.

Using Vite's dev server? Visitors can't load CSS and JavaScript from npm run dev on your computer. The Share tab warns you when it's running: stop it and run npm run build before sharing.

Receiving webhooks

Give the provider your link plus the webhook path, for example https://quiet-river-1234.trycloudflare.com/stripe/webhook. With Only with a password on, webhook routes found by the Webhooks page stay open without the password, because providers can't type one.

Quick tunnel addresses change every time you start a link, so update the address at the provider when you share again. With Pro, the Webhooks page records every delivery and can replay it, so you rarely need the provider to send it again.

Keep in mind

  • Anyone with the address reaches your site and its local data. Use a password for anything private, and a short duration.
  • Don't share a site with APP_DEBUG=true and real secrets in .env to people you don't trust: error pages show details.
  • Quick tunnels are meant for development and demos, not for hosting.