devCommand

Catches the setup problems before they catch you.

Missing vendor folder, no node_modules, keys missing from .env, debug on in production. devCommand spots them from files alone and offers the fix.

Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel

1

File-only

Every check reads files. Nothing is started to look.

2

A fix for each

Each finding comes with a one-click command, or a snippet to paste.

3

.env compared

“28 keys missing from .env” — compared with .env.example, and appended for you.

4

Every stack

Flutter packages not fetched, iOS pods missing, no wp-config.php.

01

A strip, then the detail

A small strip under the commands shows how many things need attention. Open it for the full list.

  • Counted at a glance
  • Details on demand
  • A reason with every finding
02

Fixed in a click

No vendor folder? Install. No .env? Copy .env.example and generate a key. Missing keys? Append them.

  • The fix command is shown first
  • Runs in a normal tab
  • Or copy the snippet instead
03

Flutter and WordPress too

Packages not fetched, pods missing for iOS, or a WordPress install without its config.

  • pub get as the fix
  • pod install as the fix
  • Clear guidance for wp-config.php

The small things

Details that add up.

Debug in production

APP_ENV=production with APP_DEBUG=true is flagged.

Log folder writable

Checked, so errors can actually be written.

New clone friendly

Clone, add, fix everything it lists, run.

Quiet when fine

No strip at all when there’s nothing to say.

Never automatic

Fixes only run when you press them.

Readable reasons

Each finding says why it matters.

Free, and ready when you are.

No account, no licence key. Point devCommand at ~/Sites and press your first command.

macOS 14 Sonoma or later · Apple silicon and Intel · Version 1.0