Skip to main content

The Ultimate Guide to Terminus Commands

One breezy, late-winter morning, I found myself ankle-deep in one of those old projects—ones you tuck away, promising to revisit soon—like a gardener scouring through weeds. I needed to fix a bug in an application that had been long forgotten. Given my rusty skills and the urgency of the task, I called in reinforcements—my good friend and tech wizard, Mark. As usual, he came armed with caffeine and an indecipherable mug of wisdom: “Dude, you need the ninja secrets of Terminus.” And there began our adventure into the mystical realm of Terminus commands.

Striding through the wave of memories, I feel a burst of affection for those times Mark and I would chase down coding conundrums like caffeine-fueled detectives. So here it is, our carefully gleaned knowledge: The Ultimate Guide to Terminus Commands.

The Dawn of Discernment: Getting Started with Terminus​

Fresh to the experience, navigating Terminus feels like deciphering hieroglyphics. Mark and I sat down that afternoon, keyboards aflame. “You initiate the rabbit hole with terminus auth:login,” Mark informed me, grinning as though revealing a magician’s trick.

Step by Step: Logging In​

terminus auth:login

The screen blinked. I fumbled through inputting my credentials—not unlike stumbling in the dark searching for the light switch. Easier with Mark’s knowing eyes over my shoulder. Nothing complex, yet? Well, let’s keep marching along this road, shall we?

In those tiny triumphs, joy soared like a small paper plane catching a gust of wind. “Easy, right?" Mark chuckled. Indeed. For the greenhorn explorer, logging in is just the beginning.

Exploring the Treasure Map: Site Management​

With a dash of marvel, akin to unearthing a quirky trinket from the attic, we delved into site management commands. Naturally, Mark led the way. “Now that you’re in,” he started, his eyes lighting up like those of a mentor unveiling cherished arcane lore, “it’s time to list the sites.”

Step by Step: List Your Sites​

terminus site:list

Ah, the satisfaction of seeing my forgotten world of projects displayed in an orderly list on the screen. Revel in these moments; they’re breadcrumbs leading us deeper into this labyrinth.

A soft chuckle resonates as I recall Mark giving all those throwaway sites nicknames. There is something profoundly satisfying in naming the digital creatures we create, isn't there? Like naming goldfish—giving significance to our little confetti in the universe.

Unraveling Mysteries: Gizmos and Widgets—Backups​

Ah, the bittersweet embrace of nostalgia. Recall the time when projects needed a good ol’ backup—a digital insurance policy, of sorts. Mark nudged me out of my reverie: “Now, for making backups, try this.”

Step by Step: Create a Backup​

terminus backup:create --site=<site-name> --env=<environment>

Commands like these are akin to doing dishes: not glamorous, but oh-so-important. A bit repetitious but with a rewarding aftertaste, like brownie batter off a spoon, minus the sugar high.

We celebrated not with cake but with a hearty high-five—a camaraderie cemented over ones and zeroes. "Crisis averted!" we’d yell triumphantly, our spirits dancing like buoyant kites in sunny skies.

The Dance of Deployment: Implementing Changes​

Deploying changes? Oh, those were times filled with adrenaline. Mark would always say, “It’s like spelunking, except with fewer bats and more code.” Our code deployed smoother than a fox on ice skates, with a little help from this trusty incantation.

Step by Step: Deploy a Code​

terminus env:deploy --site=<site-name> --env=<environment> --note=<your-note>

Ahh, sensory joy. The satisfaction of seeing those changes seep through the fabric of reality—or code, rather. A note to capture the moment: “Fixed that… thing.” It’s our digital scrapbook, piecing together snapshots of victories big and small.

A Stroll with the Sorcerer’s Wand: Cloning Environments​

Remember that tingle of anticipation as you walked through an open-air market, not knowing what treasures lay beyond the next stall? That was us, cloning dev environments. “Copy, but meticulously,” said wise Mark. He showed me the next command.

Step by Step: Clone an Environment​

terminus env:clone-content --site=<site-name> --from-env=<source-env> --to-env=<destination-env> --db-only

Oh, the glee of crafting these parallel universe-like environments! It felt like building a ship in a bottle—crafty, clever. Mark and I prided ourselves on being jolly good artisans of our digital realms.

Sweat Not the Small Stuff: All the Little Helpers​

Mark loved shortcuts. “They save time for things like eating tacos,” he’d joke. Soon he unveiled his treasure chest filled with those lesser-known nuggets.

Step by Step: Unlocking Cheats​

  • Clear Site Caches:

    terminus env:clear-cache --site=<site-name> --env=<environment>

  • Retrieve Connection Info:

    terminus connection:info --site=<site-name> --env=<environment>

Finding these shortcuts gave our workflows wings. With every command, a renewed sense of wizardry blossomed. Like finding a forgotten bookmark in a very good book—unexpected yet delightful.

Reflections on Our Odyssey​

Ah, dear Mark. A titan of patience and cheer. We spent countless hours roaming the corridors of code—his laughter echoing like wind chimes on a warm summer night all along our path of discovery.

Navigating Terminus became less of a chore and more like crafting poetry. Precision and rhythm, all tidied together into a symphony befitting any seasoned web enthusiast. At day’s end, armed with our newfound knowledge, we mused: “What’s next on our quest?” His replied: “Ice cream?”

So, here’s to those of us clutching our trusty digital compasses—venturing bravely into line after line of encoded magic. Go forth and command, intrepid adventurers. For amid these lines lies the heart of discovery, best shared with a friend and celebrated with laughter.