Temporary Local Folder Sharing Without Uploads: When It Makes Sense Instead of Drive, nginx, or croc

#webdev #productivity #cli #devops

There is a small workflow tax I keep seeing developers tolerate

The folder is already on your machine
Someone else needs to inspect it

So you end up doing the whole dance:

zip it
upload it
wait for it to sync
fix permissions
explain where to click

That is fine if it happens once
It gets annoying when it happens every week with client folders, build outputs, generated docs or release artifacts.

I have been thinking about the boundary here. When does sharing a local folder deserve proper hosting and when is a temporary link enough?

Permanent Hosting vs Temporary Sharing

Temporary sharing is not permanent hosting

Permanent hosting is when files need to live somewhere and stay up reliably
Temporary sharing is when one person needs to inspect the files, and then the share can disappear

If you just need someone to review a dist/ folder, deploying it to Vercel or Netlify is often overkill

Why the usual tools feel awkward

We all have tools we trust, but they fit different jobs:

Drive / Dropbox: Good when files should live in cloud storage. But uploading is the exact work you are trying to avoid when the folder is already local and temporary
nginx: Good for permanent hosting. Heavy for a 20-minute review
croc: Great for CLI-to-CLI transfer. But if the recipient just wants a browser link, it does not fit
python -m http.server: Good for the LAN. But public access, passwords, and shutdown behavior become your problem

The narrow gap is: local folder -> browser link -> stop when done

The Local Bridge Workflow

I kept running into this gap, so I built a small CLI to solve it

The workflow is intentionally boring. You point it at a folder, set a password and it gives you a public browser link using an outbound Cloudflare tunnel. The recipient opens the link, types the password, and brows the files

No inbound ports opened. No uploading the folder first

Trust Boundaries

Local files plus an executable plus a tunnel is a category where trust matters. This is controlled temporary sharing, not enterprise file governance

If you are setting up a workflow like this, the safe mental model is:

expose only the folder you intend to share
use .lbignore to exclude .env or sensitive files
use passwords for shared sessions
stop the share when the handoff is done

The Packaging Question

Can you wire this up yourself? Yes. You can connect a local server to a tunnel and add auth

The real question is whether the workflow repeats often enough that you want a packaged tool. If you only do this once a year, write a script or just use Drive

If you do client handoffs, build reviews, or artifact sharing every week, the repeated tax might be worth removing

If you are curious about the architecture of exposing local folders, or want to see the specific security model and VirusTotal scans for Local Bridge, I documented the proof and trust boundaries here:
Local Bridge Architecture & Proof

Disclosure: I build Local Bridge, a paid CLI in this category. This article is about the workflow and tradeoffs, not a claim that one tool fits every case.