Sync .env and other ignored files
1:38 · 5 chapters ·
Git leaves your .env files, local config and certificates behind, so a second computer can't run the project. Sync Ignored Files in lpm copies what git ignores between your computers, shows what differs key by key, and keeps the ticked files the same from then on.
Transcript
The narration, chapter by chapter. Pick a time to play from there.
Intro
Git never copies your .env to your other computer. lpm does, and keeps it the same on both.
Why sync them
Your storefront project is on this Mac and on your Mac mini, cloned from the same repository. But git leaves out what it ignores, so the Mac mini is missing your keys and local settings.
Pick the files
Right-click storefront and choose Sync Ignored Files. At the top are the two computers it keeps the same: this Mac, and the Mac mini. Below is everything git ignores, on either one, and where each file is. Your local settings and certificates are only on this Mac. lpm has already ticked your secrets and local config, and left heavy folders like node_modules out. Your .env is on both, but the Mac mini's is older. Click Compare to see it key by key, with the values hidden: the Stripe key is new here.
Sync
Where they differ, lpm keeps the newest copy. Click Sync, and the files are copied to the Mac mini. From now on, they stay the same both ways, whenever both computers are connected.
Check the Mac mini
Click Done, and open storefront on the Mac mini. Press Command Shift E to see its files. Your .env is there now, with the Stripe key. Tick your ignored files once, and every computer you work on has them.
