GuideDecember 8, 20265 min read

Conference Talk Setup: Get Your Demo Environment Running in 60 Seconds

Borrowed laptop, conference WiFi, five minutes to setup. Here is how ConfigSync gets your demo running in 60 seconds flat.

The Conference Demo Nightmare

You have rehearsed your talk a dozen times. Your slides are polished. Your demo is impressive. Then you arrive at the conference and discover the AV setup requires an HDMI adapter you do not have, so you borrow the organizer's laptop. Now you have fifteen minutes to get your entire demo environment running on a machine that has never seen your code.

Or maybe your own laptop decides to install a macOS update overnight and something breaks. Or the venue's WiFi blocks the ports you need. Or you left your power adapter at the hotel and the borrowed machine has a different charger.

The common thread is that conference demos require setup on unfamiliar machines under time pressure. ConfigSync turns this from a panic-inducing ordeal into a single command.

Pre-Conference Preparation

The key is preparing a dedicated demo profile before the conference. This profile contains only what your demo needs, nothing more. Fewer configs means faster pulls and less that can go wrong.

Create a demo profile
# Create a minimal demo profile $ configsync profile create conference-demo \ --path ~/demo \ --env development # Add only what the demo needs $ configsync profile config conference-demo \ modules "git,shell,node" # Add demo-specific environment variables $ configsync profile secret conference-demo DEMO_API_KEY $ configsync profile env conference-demo ~/demo/app/.env.local # Push the profile $ configsync push -m "Conference demo profile"
Keep your demo profile minimal. The less you pull, the faster the setup and the fewer things that can break. If your demo only needs Node.js and a git repo, do not pull your entire Vim config and Docker setup.

The 60-Second Setup

On the day of the talk, you open a terminal on whatever machine is available and run one command:

One-command demo setup
# Generate a one-time setup token from your dashboard # or from your phone: configsync.dev/dashboard/tokens # On the borrowed machine: $ curl -fsSL configsync.dev/install?token=cs_demo_abc123 | sh # This installs ConfigSync, authenticates, and pulls # only the conference-demo profile: Installing ConfigSync... done. Authenticating... done. Pulling profile: conference-demo ✓ git config (2 files) ✓ shell config (1 file) ✓ node config (1 file) ✓ 1 env file (encrypted) Restored in 12s.

Twelve seconds for configs. Now clone your demo repo and start the dev server:

Bootstrap the demo
# Your bootstrap script handles the rest $ ~/.configsync/bootstrap.sh Cloning demo repository... Installing dependencies (npm ci)... Starting dev server on http://localhost:3000... Demo ready. Total time: 58 seconds.

The Bootstrap Script

The bootstrap script is where you encode everything beyond config files. It clones your demo repo, installs dependencies, and starts the dev server.

~/.configsync/demo-bootstrap.sh
#!/bin/bash set -e DEMO_DIR="$HOME/demo" # Clone the demo repo if not present if [ ! -d "$DEMO_DIR/app" ]; then git clone https://github.com/you/conference-demo.git "$DEMO_DIR/app" fi cd "$DEMO_DIR/app" # Install dependencies npm ci --prefer-offline 2>/dev/null || npm install # Seed demo data if needed npm run seed:demo 2>/dev/null || true # Start the dev server in the background npm run dev & echo "" echo "Demo running at http://localhost:3000" echo "Press Ctrl+C to stop."

Practice the Pull

The most important step happens before the conference. Test your setup flow on a different machine or in a fresh user account. Verify that:

  • The install command works without sudo on macOS and Linux
  • Your demo profile pulls everything it needs and nothing it does not
  • The bootstrap script handles missing dependencies gracefully
  • The demo works on both macOS and Linux (in case the borrowed machine is a Chromebook running Linux)
  • The total time from empty terminal to running demo is under two minutes
Create a one-time token with a short expiry for the conference. If the token is intercepted on conference WiFi, it expires before anyone can misuse it. You can always generate a new one from your phone.

After the Talk: Clean Up

On a borrowed machine, you should remove your configs when you are done. ConfigSync makes this easy:

Clean up after the demo
# Remove all ConfigSync data from this machine $ configsync logout --purge Removing configs restored by ConfigSync... Removing cached data... Removing authentication tokens... Cleanup complete. No trace of your configs remains.

The --purge flag removes every file that ConfigSync placed on the machine. Your SSH keys, environment variables, and demo credentials are gone. The borrowed laptop is back to its original state, and you just delivered a flawless demo that started in under sixty seconds.

Ready to try ConfigSync?

Sync your entire dev environment across machines in minutes. Free forever for up to 3 devices.

Get StartedRead the Docs