@loopress/cli

v0.25.0

Published

a day ago

CLI tool for syncing WordPress code snippets, plugins, and Composer dependencies via the REST API

0High
0Medium
0Low

jean-smaug

oclif

Loopress

CLI to interact with the Loopress ecosystem

Usage

$ npm install -g @loopress/cli
$ lps COMMAND
running command...
$ lps (--version)
@loopress/cli/0.25.0 linux-x64 node-v24.20.0
$ lps --help [COMMAND]
USAGE
  $ lps COMMAND
...

Error reporting

Loopress sends crash reports to our Sentry project so we can find and fix bugs.

To opt out, either:

run lps telemetry disable (persists across all future commands), or
set LOOPRESS_TELEMETRY_DISABLED=1 (overrides the persisted preference for a single run, useful in CI).

A crash report includes the command name, its flags/args as typed, your Node.js version, and OS. WordPress credentials are configured via lps project config and are never passed as command-line arguments, so they don't end up in a report.

Commands

`lps acf diff [PATH]`

Show what differs in ACF field groups, post types, taxonomies, and options pages between your local files and a WordPress environment, or between two environments

USAGE
  $ lps acf diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to ACF directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in ACF field groups, post types, taxonomies, and options pages between your local files and a
  WordPress environment, or between two environments

EXAMPLES
  $ lps acf diff

  $ lps acf diff --env staging

  $ lps acf diff --env staging --against production

See code: src/commands/acf/diff.ts

`lps acf list`

List ACF field groups, post types, taxonomies, and options pages from WordPress

USAGE
  $ lps acf list [--json] [--env <value>] [--type field-groups|post-types|taxonomies|options-pages...]

FLAGS
  --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
  --type=<option>...  Limit to specific ACF object types
                      <options: field-groups|post-types|taxonomies|options-pages>

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List ACF field groups, post types, taxonomies, and options pages from WordPress

EXAMPLES
  $ lps acf list

  $ lps acf list --type field-groups

See code: src/commands/acf/list.ts

`lps acf pull [PATH]`

Pull ACF field groups, post types, taxonomies, and options pages from WordPress

USAGE
  $ lps acf pull [PATH] [--env <value>] [-d] [-y] [--type field-groups|post-types|taxonomies|options-pages...]

ARGUMENTS
  [PATH]  Path to ACF directory (overrides project config)

FLAGS
  -d, --dry-run           Show what would change without making changes
  -y, --yes               Answer yes to confirmation prompts
      --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
      --type=<option>...  Limit to specific ACF object types
                          <options: field-groups|post-types|taxonomies|options-pages>

DESCRIPTION
  Pull ACF field groups, post types, taxonomies, and options pages from WordPress

EXAMPLES
  $ lps acf pull

  $ lps acf pull --type field-groups

See code: src/commands/acf/pull.ts

`lps acf push [PATH]`

Push ACF field groups, post types, taxonomies, and options pages to WordPress

USAGE
  $ lps acf push [PATH] [--env <value>] [-d] [-y] [--type field-groups|post-types|taxonomies|options-pages...]

ARGUMENTS
  [PATH]  Path to ACF directory (overrides project config)

FLAGS
  -d, --dry-run           Show what would change without making changes
  -y, --yes               Answer yes to confirmation prompts
      --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
      --type=<option>...  Limit to specific ACF object types
                          <options: field-groups|post-types|taxonomies|options-pages>

DESCRIPTION
  Push ACF field groups, post types, taxonomies, and options pages to WordPress

EXAMPLES
  $ lps acf push

  $ lps acf push --type field-groups

See code: src/commands/acf/push.ts

`lps acf rollback [PATH]`

Restore ACF field groups, post types, taxonomies, and options pages to a snapshot taken automatically before an earlier lps acf push

USAGE
  $ lps acf rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to ACF directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore ACF field groups, post types, taxonomies, and options pages to a snapshot taken automatically before an
  earlier `lps acf push`

EXAMPLES
  $ lps acf rollback

  $ lps acf rollback --list

  $ lps acf rollback --to 1732000000000

  $ lps acf rollback --dry-run

See code: src/commands/acf/rollback.ts

`lps api diff [PATH]`

Show what differs in custom API route files between your local files and a WordPress environment, or between two environments

USAGE
  $ lps api diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to api directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in custom API route files between your local files and a WordPress environment, or between two
  environments

EXAMPLES
  $ lps api diff

  $ lps api diff --env staging

  $ lps api diff --env staging --against production

See code: src/commands/api/diff.ts

`lps api list`

List custom API route files from WordPress

USAGE
  $ lps api list [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List custom API route files from WordPress

EXAMPLES
  $ lps api list

See code: src/commands/api/list.ts

`lps api publish [PATH]`

Publish custom API routes to your Loopress account so they can be deployed to other projects. Does not touch any WordPress site.

USAGE
  $ lps api publish [PATH]

ARGUMENTS
  [PATH]  Path to api directory (overrides project config)

DESCRIPTION
  Publish custom API routes to your Loopress account so they can be deployed to other projects. Does not touch any
  WordPress site.

EXAMPLES
  $ lps api publish

  $ lps api publish --path ./api

See code: src/commands/api/publish.ts

`lps api pull [PATH]`

Pull custom API route files from WordPress

USAGE
  $ lps api pull [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to api directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull custom API route files from WordPress

EXAMPLES
  $ lps api pull

  $ lps api pull --path ./api

See code: src/commands/api/pull.ts

`lps api push [PATH]`

Push custom API route files to WordPress

USAGE
  $ lps api push [PATH] [--json] [--env <value>] [-d] [-y] [--prune]

ARGUMENTS
  [PATH]  Path to api directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --prune        Delete server-side route files not present locally after pushing

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push custom API route files to WordPress

EXAMPLES
  $ lps api push

  $ lps api push --path ./api

  $ lps api push --prune

See code: src/commands/api/push.ts

`lps api rm FILENAME`

Remove a custom API route file from WordPress

USAGE
  $ lps api rm FILENAME [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  FILENAME  The route file to remove, its slug without the .php extension (e.g. "hello" or "invoice-pdf/[order_id]")

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Remove a custom API route file from WordPress

EXAMPLES
  $ lps api rm hello

  $ lps api rm hello --yes

See code: src/commands/api/rm.ts

`lps api rollback [PATH]`

Restore API route files to a snapshot taken automatically before an earlier lps api push

USAGE
  $ lps api rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to api directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore API route files to a snapshot taken automatically before an earlier `lps api push`

EXAMPLES
  $ lps api rollback

  $ lps api rollback --list

  $ lps api rollback --to 1732000000000

  $ lps api rollback --dry-run

See code: src/commands/api/rollback.ts

`lps app list`

List single-page apps deployed to WordPress

USAGE
  $ lps app list [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List single-page apps deployed to WordPress

EXAMPLES
  $ lps app list

See code: src/commands/app/list.ts

`lps app pull [PATH]`

Pull single-page app bundles from WordPress into local files

USAGE
  $ lps app pull [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to apps directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull single-page app bundles from WordPress into local files

EXAMPLES
  $ lps app pull

See code: src/commands/app/pull.ts

`lps app push [NAME]`

Push built single-page app bundles to WordPress. Each app is an apps/<name>/ directory holding a loopress.app.json and a built dist/ folder. Only files whose content changed are uploaded.

USAGE
  $ lps app push [NAME] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [NAME]  Push only this app (defaults to every app in the directory)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push built single-page app bundles to WordPress. Each app is an `apps/<name>/` directory holding a loopress.app.json
  and a built dist/ folder. Only files whose content changed are uploaded.

EXAMPLES
  $ lps app push

  $ lps app push search

See code: src/commands/app/push.ts

`lps app remove NAME`

Remove a single-page app from WordPress: deletes its bundle from wp-content/loopress/apps/ and unregisters the shortcode. Local files are left untouched.

USAGE
  $ lps app remove NAME [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  NAME  App to remove from WordPress

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Remove a single-page app from WordPress: deletes its bundle from wp-content/loopress/apps/ and unregisters the
  shortcode. Local files are left untouched.

EXAMPLES
  $ lps app remove search

See code: src/commands/app/remove.ts

`lps composer init`

Create a composer.json wired to WPackagist for installing WordPress.org plugins and themes

USAGE
  $ lps composer init [--env <value>] [-d]

FLAGS
  -d, --dry-run      Show what would change without making changes
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Create a composer.json wired to WPackagist for installing WordPress.org plugins and themes

EXAMPLES
  $ lps composer init

  $ lps composer init --dry-run

See code: src/commands/composer/init.ts

`lps composer pull`

Pull composer.json and composer.lock from WordPress

USAGE
  $ lps composer pull [--json] [--env <value>] [-d]

FLAGS
  -d, --dry-run      Show what would change without making changes
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull composer.json and composer.lock from WordPress

EXAMPLES
  $ lps composer pull

  $ lps composer pull --dry-run

See code: src/commands/composer/pull.ts

`lps composer push`

Push composer.json to WordPress and run Composer to resolve and install dependencies

USAGE
  $ lps composer push [--json] [--env <value>] [-d] [-y] [--force]

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --force        Allow downgrades and take over plugins/themes installed outside Loopress

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push composer.json to WordPress and run Composer to resolve and install dependencies

EXAMPLES
  $ lps composer push

  $ lps composer push --dry-run

See code: src/commands/composer/push.ts

`lps dev`

Watch project files and push changes to the local WordPress instance as they happen. Always targets the "local" environment, run lps snippet push etc. directly for any other environment.

USAGE
  $ lps dev [--only <value>] [--skip <value>]

FLAGS
  --only=<value>  Only watch these resource types (comma-separated): snippets, api, plugins
  --skip=<value>  Skip these resource types (comma-separated): snippets, api, plugins

DESCRIPTION
  Watch project files and push changes to the local WordPress instance as they happen. Always targets the "local"
  environment, run `lps snippet push` etc. directly for any other environment.

EXAMPLES
  $ lps dev

  $ lps dev --only=snippets,api

  $ lps dev --skip=plugins

See code: src/commands/dev.ts

`lps diff`

Show what differs between your local tracked files and a WordPress environment, or between two environments. Covers snippets, forms, ACF, API routes, Hooks, SEO, Options, Menus, Theme styles, and Composer. Plugins and themes have their own lps plugin status / lps theme status. Exit code: 0 in sync, 1 on drift, 2 when a resource could not be compared, so it doubles as a CI drift gate.

USAGE
  $ lps diff [--json] [--env <value>] [--against <value>] [--only
    snippet|form|acf|api|hook|seo|menu|option|theme-styles|composer...] [--skip
    snippet|form|acf|api|hook|seo|menu|option|theme-styles|composer...]

FLAGS
  --against=<value>   Compare the primary environment against this second environment instead of against local files
  --env=<value>       Target environment by name, overriding the globally active one (lps project switch)
  --only=<option>...  Only compare these resources
                      <options: snippet|form|acf|api|hook|seo|menu|option|theme-styles|composer>
  --skip=<option>...  Compare every resource except these
                      <options: snippet|form|acf|api|hook|seo|menu|option|theme-styles|composer>

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs between your local tracked files and a WordPress environment, or between two environments. Covers
  snippets, forms, ACF, API routes, Hooks, SEO, Options, Menus, Theme styles, and Composer. Plugins and themes have
  their own `lps plugin status` / `lps theme status`. Exit code: 0 in sync, 1 on drift, 2 when a resource could not be
  compared, so it doubles as a CI drift gate.

EXAMPLES
  $ lps diff

  $ lps diff --env staging

  $ lps diff --env staging --against production

  $ lps diff --only snippet --only acf

  $ lps diff --skip composer

See code: src/commands/diff.ts

`lps doctor`

Diagnose connectivity, plugin and credential problems for the targeted environment

USAGE
  $ lps doctor [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Diagnose connectivity, plugin and credential problems for the targeted environment

EXAMPLES
  $ lps doctor

  $ lps doctor --env production

See code: src/commands/doctor.ts

`lps form diff [PATH]`

Show what differs in forms between your local files and a WordPress environment, or between two environments

USAGE
  $ lps form diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to forms directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in forms between your local files and a WordPress environment, or between two environments

EXAMPLES
  $ lps form diff

  $ lps form diff --env staging

  $ lps form diff --env staging --against production

See code: src/commands/form/diff.ts

`lps form list`

List forms from WordPress

USAGE
  $ lps form list [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List forms from WordPress

EXAMPLES
  $ lps form list

See code: src/commands/form/list.ts

`lps form pull [PATH]`

Pull forms from WordPress

USAGE
  $ lps form pull [PATH] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to forms directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Pull forms from WordPress

EXAMPLES
  $ lps form pull

See code: src/commands/form/pull.ts

`lps form push [PATH]`

Push forms to WordPress. Local files created or updated remotely are renamed on disk to the <id>-<slug>.json convention.

USAGE
  $ lps form push [PATH] [--env <value>] [-d] [-y] [--allow-notifications]

ARGUMENTS
  [PATH]  Path to forms directory (overrides project config)

FLAGS
  -d, --dry-run              Show what would change without making changes
  -y, --yes                  Answer yes to confirmation prompts
      --allow-notifications  Also push each form's notification and confirmation settings (recipients, sender,
                             messages). Off by default: the server keeps its own so a stray push can't redirect
                             submissions.
      --env=<value>          Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Push forms to WordPress. Local files created or updated remotely are renamed on disk to the `<id>-<slug>.json`
  convention.

EXAMPLES
  $ lps form push

  $ lps form push --allow-notifications

See code: src/commands/form/push.ts

`lps form rollback [PATH]`

Restore forms to a snapshot taken automatically before an earlier lps form push

USAGE
  $ lps form rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to forms directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore forms to a snapshot taken automatically before an earlier `lps form push`

EXAMPLES
  $ lps form rollback

  $ lps form rollback --list

  $ lps form rollback --to 1732000000000

  $ lps form rollback --dry-run

See code: src/commands/form/rollback.ts

`lps help [COMMAND]`

Display help for lps.

USAGE
  $ lps help [COMMAND...] [-n]

ARGUMENTS
  [COMMAND...]  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for lps.

See code: @oclif/plugin-help

`lps hook diff [PATH]`

Show what differs in hook files between your local files and a WordPress environment, or between two environments

USAGE
  $ lps hook diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to hooks directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in hook files between your local files and a WordPress environment, or between two environments

EXAMPLES
  $ lps hook diff

  $ lps hook diff --env staging

  $ lps hook diff --env staging --against production

See code: src/commands/hook/diff.ts

`lps hook list`

List hook files (actions, filters, cron) from WordPress

USAGE
  $ lps hook list [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List hook files (actions, filters, cron) from WordPress

EXAMPLES
  $ lps hook list

See code: src/commands/hook/list.ts

`lps hook pull [PATH]`

Pull hook files (actions, filters, cron) from WordPress

USAGE
  $ lps hook pull [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to hooks directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull hook files (actions, filters, cron) from WordPress

EXAMPLES
  $ lps hook pull

  $ lps hook pull --path ./hooks

See code: src/commands/hook/pull.ts

`lps hook push [PATH]`

Push hook files (actions, filters, cron) to WordPress

USAGE
  $ lps hook push [PATH] [--json] [--env <value>] [-d] [-y] [--prune]

ARGUMENTS
  [PATH]  Path to hooks directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --prune        Delete server-side hook files not present locally after pushing

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push hook files (actions, filters, cron) to WordPress

EXAMPLES
  $ lps hook push

  $ lps hook push --path ./hooks

  $ lps hook push --prune

See code: src/commands/hook/push.ts

`lps hook rm FILENAME`

Remove a hook file (action, filter, cron) from WordPress

USAGE
  $ lps hook rm FILENAME [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  FILENAME  The hook file to remove, its slug without the .php extension (e.g. "hello" or "invoice-pdf/[order_id]")

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Remove a hook file (action, filter, cron) from WordPress

EXAMPLES
  $ lps hook rm hello

  $ lps hook rm hello --yes

See code: src/commands/hook/rm.ts

`lps hook rollback [PATH]`

Restore hook files to a snapshot taken automatically before an earlier lps hook push

USAGE
  $ lps hook rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to hooks directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore hook files to a snapshot taken automatically before an earlier `lps hook push`

EXAMPLES
  $ lps hook rollback

  $ lps hook rollback --list

  $ lps hook rollback --to 1732000000000

  $ lps hook rollback --dry-run

See code: src/commands/hook/rollback.ts

`lps init`

Initialize a loopress.json config file in the current directory

USAGE
  $ lps init

DESCRIPTION
  Initialize a loopress.json config file in the current directory

EXAMPLES
  $ lps init

See code: src/commands/init.ts

`lps login`

USAGE
  $ lps login

DESCRIPTION
  Log in to the Loopress console

EXAMPLES
  $ lps login

See code: src/commands/login.ts

`lps logout`

Log out from the Loopress console

USAGE
  $ lps logout

DESCRIPTION
  Log out from the Loopress console

EXAMPLES
  $ lps logout

See code: src/commands/logout.ts

`lps menu diff [PATH]`

Show what differs in nav menus and the active theme menu locations between your local files and a WordPress environment, or between two environments

USAGE
  $ lps menu diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to menus directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in nav menus and the active theme menu locations between your local files and a WordPress
  environment, or between two environments

EXAMPLES
  $ lps menu diff

  $ lps menu diff --env staging

  $ lps menu diff --env staging --against production

See code: src/commands/menu/diff.ts

`lps menu list`

List nav menus and the active theme menu locations on WordPress

USAGE
  $ lps menu list [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List nav menus and the active theme menu locations on WordPress

EXAMPLES
  $ lps menu list

See code: src/commands/menu/list.ts

`lps menu pull [PATH]`

Pull nav menus and the active theme menu locations from WordPress

USAGE
  $ lps menu pull [PATH] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to menus directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Pull nav menus and the active theme menu locations from WordPress

EXAMPLES
  $ lps menu pull

See code: src/commands/menu/pull.ts

`lps menu push [PATH]`

Push local nav menus and the active theme menu locations to WordPress. Each menu's post_type/taxonomy items are resolved by slug on the target environment, never by a raw id; an item whose target does not exist there fails the whole menu rather than guessing.

USAGE
  $ lps menu push [PATH] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to menus directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Push local nav menus and the active theme menu locations to WordPress. Each menu's post_type/taxonomy items are
  resolved by slug on the target environment, never by a raw id; an item whose target does not exist there fails the
  whole menu rather than guessing.

EXAMPLES
  $ lps menu push

See code: src/commands/menu/push.ts

`lps menu rollback [PATH]`

Restore nav menus and menu locations to a snapshot taken automatically before an earlier lps menu push

USAGE
  $ lps menu rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to menus directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore nav menus and menu locations to a snapshot taken automatically before an earlier `lps menu push`

EXAMPLES
  $ lps menu rollback

  $ lps menu rollback --list

  $ lps menu rollback --to 1732000000000

  $ lps menu rollback --dry-run

See code: src/commands/menu/rollback.ts

`lps option add NAME`

Fetch a WordPress option by name and start tracking it locally. Run lps option list first to find the name: this copies a raw value across environments, verify it does not embed post/user IDs before pushing it elsewhere.

USAGE
  $ lps option add NAME [--json] [--env <value>] [-d] [--path <value>]

ARGUMENTS
  NAME  Option name to start tracking (see `lps option list`)

FLAGS
  -d, --dry-run       Show what would change without making changes
      --env=<value>   Target environment by name, overriding the globally active one (lps project switch)
      --path=<value>  Path to options directory (overrides project config)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Fetch a WordPress option by name and start tracking it locally. Run `lps option list` first to find the name: this
  copies a raw value across environments, verify it does not embed post/user IDs before pushing it elsewhere.

EXAMPLES
  $ lps option add wpseo_titles

  $ lps option add siteurl

See code: src/commands/option/add.ts

`lps option diff [PATH]`

Show what differs, for locally tracked options, between your local files and a WordPress environment, or between two environments

USAGE
  $ lps option diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to options directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs, for locally tracked options, between your local files and a WordPress environment, or between two
  environments

EXAMPLES
  $ lps option diff

  $ lps option diff --env staging

  $ lps option diff --env staging --against production

See code: src/commands/option/diff.ts

`lps option list`

List WordPress option names currently on the site (names and autoload only, never values). CORE flags a WordPress-native default (certain); SOURCE? is a best-effort guessed plugin slug, found by name or by scanning active plugins' own PHP source (uncertain unless confirmed, occasionally wrong or blank, never trust it over CORE); PLUGIN is that slug's own declared display name, a label only, no confidence of its own. Use this to find the name of the option you want, then lps option add <name> to track it.

USAGE
  $ lps option list [--json] [--env <value>] [--no-core]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
  --no-core      Exclude WordPress-native default options and the CORE column from the output, including --json

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List WordPress option names currently on the site (names and autoload only, never values). CORE flags a
  WordPress-native default (certain); SOURCE? is a best-effort guessed plugin slug, found by name or by scanning active
  plugins' own PHP source (uncertain unless confirmed, occasionally wrong or blank, never trust it over CORE); PLUGIN is
  that slug's own declared display name, a label only, no confidence of its own. Use this to find the name of the option
  you want, then `lps option add <name>` to track it.

EXAMPLES
  $ lps option list

  $ lps option list --no-core

See code: src/commands/option/list.ts

`lps option pull [PATH]`

Refresh locally tracked options from WordPress. Options not yet tracked are never pulled, run lps option add <name> for those first.

USAGE
  $ lps option pull [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to options directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Refresh locally tracked options from WordPress. Options not yet tracked are never pulled, run `lps option add <name>`
  for those first.

EXAMPLES
  $ lps option pull

See code: src/commands/option/pull.ts

`lps option push [PATH]`

Push locally tracked, non-readonly options to WordPress (upsert only, never deletes an untracked option). Options marked "readonly": true in their local file are skipped, edit the file to override.

USAGE
  $ lps option push [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to options directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push locally tracked, non-readonly options to WordPress (upsert only, never deletes an untracked option). Options
  marked "readonly": true in their local file are skipped, edit the file to override.

EXAMPLES
  $ lps option push

See code: src/commands/option/push.ts

`lps option remove NAME`

Stop tracking an option locally and delete it from WordPress. Local untracking always happens (git-reversible); pass --local-only to skip the WordPress delete and only stop tracking.

USAGE
  $ lps option remove NAME [--json] [--env <value>] [-d] [-y] [--local-only] [--path <value>]

ARGUMENTS
  NAME  Option name to stop tracking

FLAGS
  -d, --dry-run       Show what would change without making changes
  -y, --yes           Answer yes to confirmation prompts
      --env=<value>   Target environment by name, overriding the globally active one (lps project switch)
      --local-only    Untrack locally without deleting the option on WordPress
      --path=<value>  Path to options directory (overrides project config)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Stop tracking an option locally and delete it from WordPress. Local untracking always happens (git-reversible); pass
  --local-only to skip the WordPress delete and only stop tracking.

EXAMPLES
  $ lps option remove wpseo_titles

  $ lps option remove wpseo_titles --local-only

See code: src/commands/option/remove.ts

`lps option rollback [PATH]`

Restore tracked options to a snapshot taken automatically before an earlier lps option push

USAGE
  $ lps option rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to options directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore tracked options to a snapshot taken automatically before an earlier `lps option push`

EXAMPLES
  $ lps option rollback

  $ lps option rollback --list

  $ lps option rollback --to 1732000000000

  $ lps option rollback --dry-run

See code: src/commands/option/rollback.ts

`lps plugin add SLUG`

Add a WordPress.org plugin to loopress.json

USAGE
  $ lps plugin add SLUG [--env <value>] [-d] [--version <value>]

ARGUMENTS
  SLUG  Plugin slug on WordPress.org

FLAGS
  -d, --dry-run          Show what would change without making changes
      --env=<value>      Target environment by name, overriding the globally active one (lps project switch)
      --version=<value>  Exact version to pin (default: "latest", tracked on every push)

DESCRIPTION
  Add a WordPress.org plugin to loopress.json

EXAMPLES
  $ lps plugin add woocommerce

  $ lps plugin add woocommerce --version 9.4.2

  $ lps plugin add contact-form-7 --dry-run

See code: src/commands/plugin/add.ts

`lps plugin audit`

Check the plugins in loopress.json for known vulnerabilities and health issues

USAGE
  $ lps plugin audit [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Check the plugins in loopress.json for known vulnerabilities and health issues

EXAMPLES
  $ lps plugin audit

See code: src/commands/plugin/audit.ts

`lps plugin pull`

Pull installed plugins from WordPress into loopress.json, pinned to their live versions

USAGE
  $ lps plugin pull [--json] [--env <value>] [-d]

FLAGS
  -d, --dry-run      Show what would change without making changes
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull installed plugins from WordPress into loopress.json, pinned to their live versions

EXAMPLES
  $ lps plugin pull

  $ lps plugin pull --dry-run

See code: src/commands/plugin/pull.ts

`lps plugin push`

Install plugins on WordPress to match loopress.json, pinned via Composer + WPackagist

USAGE
  $ lps plugin push [--json] [--env <value>] [-d] [-y] [--force] [--prune]

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --force        Allow downgrades and let Loopress take over plugins installed outside it (replaces their files)
      --prune        Deactivate plugins that are active on the site but absent from loopress.json

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Install plugins on WordPress to match loopress.json, pinned via Composer + WPackagist

EXAMPLES
  $ lps plugin push

  $ lps plugin push --dry-run

  $ lps plugin push --force --prune

See code: src/commands/plugin/push.ts

`lps plugin status`

Compare the plugins on WordPress against loopress.json and report drift

USAGE
  $ lps plugin status [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Compare the plugins on WordPress against loopress.json and report drift

EXAMPLES
  $ lps plugin status

See code: src/commands/plugin/status.ts

`lps project config`

Add or update a WordPress project environment. By default, authorizes via WordPress in your browser; manual username/Application Password entry is available as a fallback.

USAGE
  $ lps project config

DESCRIPTION
  Add or update a WordPress project environment. By default, authorizes via WordPress in your browser; manual
  username/Application Password entry is available as a fallback.

EXAMPLES
  $ lps project config

See code: src/commands/project/config.ts

`lps project list`

List configured WordPress projects

USAGE
  $ lps project list [--json]

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List configured WordPress projects

EXAMPLES
  $ lps project list

See code: src/commands/project/list.ts

`lps project pull`

Pull projects and environments from your Loopress account that are not configured locally yet

USAGE
  $ lps project pull

DESCRIPTION
  Pull projects and environments from your Loopress account that are not configured locally yet

EXAMPLES
  $ lps project pull

See code: src/commands/project/pull.ts

`lps project push`

Push locally configured projects, environments and credentials to your Loopress account

USAGE
  $ lps project push [-y]

FLAGS
  -y, --yes  Answer yes to confirmation prompts

DESCRIPTION
  Push locally configured projects, environments and credentials to your Loopress account

EXAMPLES
  $ lps project push

See code: src/commands/project/push.ts

`lps project remove`

Remove one or more WordPress projects or environments

USAGE
  $ lps project remove

DESCRIPTION
  Remove one or more WordPress projects or environments

EXAMPLES
  $ lps project remove

See code: src/commands/project/remove.ts

`lps project rotate`

Rotate the WordPress application password for the current (or --env) environment

USAGE
  $ lps project rotate [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Rotate the WordPress application password for the current (or --env) environment

EXAMPLES
  $ lps project rotate

  $ lps project rotate --env staging

See code: src/commands/project/rotate.ts

`lps project switch`

Switch the active project and environment

USAGE
  $ lps project switch

DESCRIPTION
  Switch the active project and environment

EXAMPLES
  $ lps project switch

See code: src/commands/project/switch.ts

`lps promote FROM TO`

Copy every tracked resource from one environment to another by pulling from then pushing to . Local tracked files are overwritten with in the process.

USAGE
  $ lps promote FROM TO [--json] [-d] [-y]

ARGUMENTS
  FROM  Environment to copy the configuration from
  TO    Environment to copy the configuration to

FLAGS
  -d, --dry-run  Show what would change without making changes
  -y, --yes      Answer yes to confirmation prompts

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Copy every tracked resource from one environment to another by pulling from <from> then pushing to <to>. Local tracked
  files are overwritten with <from> in the process.

EXAMPLES
  $ lps promote staging production

  $ lps promote production staging --dry-run

See code: src/commands/promote.ts

`lps pull`

Pull all content, plugins, composer dependencies, ACF, API routes, hooks, forms, SEO, menus, options, and snippets, from WordPress

USAGE
  $ lps pull [--json] [--env <value>] [-d] [-y]

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull all content, plugins, composer dependencies, ACF, API routes, hooks, forms, SEO, menus, options, and snippets,
  from WordPress

EXAMPLES
  $ lps pull

  $ lps pull --env staging

  $ lps pull --dry-run

See code: src/commands/pull.ts

`lps push`

Push all local content, plugins, composer dependencies, ACF, API routes, hooks, forms, SEO, menus, options, and snippets, to WordPress

USAGE
  $ lps push [--json] [--env <value>] [-d] [-y]

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push all local content, plugins, composer dependencies, ACF, API routes, hooks, forms, SEO, menus, options, and
  snippets, to WordPress

EXAMPLES
  $ lps push

  $ lps push --env staging

  $ lps push --dry-run

See code: src/commands/push.ts

`lps seo diff [PATH]`

Show what differs in SEO settings, post meta, and redirects between your local files and a WordPress environment, or between two environments

USAGE
  $ lps seo diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to SEO directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in SEO settings, post meta, and redirects between your local files and a WordPress environment, or
  between two environments

EXAMPLES
  $ lps seo diff

  $ lps seo diff --env staging

  $ lps seo diff --env staging --against production

See code: src/commands/seo/diff.ts

`lps seo list`

List posts with SEO meta, and redirects if supported by the active SEO plugin, on WordPress

USAGE
  $ lps seo list [--json] [--env <value>] [--post-type <value>...]

FLAGS
  --env=<value>           Target environment by name, overriding the globally active one (lps project switch)
  --post-type=<value>...  Limit to specific post types

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List posts with SEO meta, and redirects if supported by the active SEO plugin, on WordPress

EXAMPLES
  $ lps seo list

  $ lps seo list --post-type post

See code: src/commands/seo/list.ts

`lps seo pull [PATH]`

Pull SEO settings, post meta, and (if supported) redirects from WordPress

USAGE
  $ lps seo pull [PATH] [--env <value>] [-d] [-y] [--post-type <value>...]

ARGUMENTS
  [PATH]  Path to SEO directory (overrides project config)

FLAGS
  -d, --dry-run               Show what would change without making changes
  -y, --yes                   Answer yes to confirmation prompts
      --env=<value>           Target environment by name, overriding the globally active one (lps project switch)
      --post-type=<value>...  Limit post meta to specific post types

DESCRIPTION
  Pull SEO settings, post meta, and (if supported) redirects from WordPress

EXAMPLES
  $ lps seo pull

  $ lps seo pull --post-type post --post-type page

See code: src/commands/seo/pull.ts

`lps seo push [PATH]`

Push SEO settings, post meta, and redirects to WordPress. Local redirect files created remotely are renamed on disk to the <id>-<slug> convention. Fails clearly per file if the active SEO plugin does not support redirects.

USAGE
  $ lps seo push [PATH] [--env <value>] [-d] [-y] [--allow-external-redirects]

ARGUMENTS
  [PATH]  Path to SEO directory (overrides project config)

FLAGS
  -d, --dry-run                   Show what would change without making changes
  -y, --yes                       Answer yes to confirmation prompts
      --allow-external-redirects  Allow pushing a redirect whose target points off this site. Off by default: the server
                                  rejects an off-site `urlTo` so a stray push can't 301 traffic away.
      --env=<value>               Target environment by name, overriding the globally active one (lps project switch)

DESCRIPTION
  Push SEO settings, post meta, and redirects to WordPress. Local redirect files created remotely are renamed on disk to
  the `<id>-<slug>` convention. Fails clearly per file if the active SEO plugin does not support redirects.

EXAMPLES
  $ lps seo push

  $ lps seo push --allow-external-redirects

See code: src/commands/seo/push.ts

`lps seo rollback [PATH]`

Restore SEO settings, post meta, and redirects to a snapshot taken automatically before an earlier lps seo push

USAGE
  $ lps seo rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to SEO directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)
      --list         List available snapshots instead of rolling back
      --to=<value>   Roll back to this snapshot id instead of the most recent one

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Restore SEO settings, post meta, and redirects to a snapshot taken automatically before an earlier `lps seo push`

EXAMPLES
  $ lps seo rollback

  $ lps seo rollback --list

  $ lps seo rollback --to 1732000000000

  $ lps seo rollback --dry-run

See code: src/commands/seo/rollback.ts

`lps snippet diff [PATH]`

Show what differs in snippets between your local files and a WordPress environment, or between two environments

USAGE
  $ lps snippet diff [PATH] [--json] [--env <value>] [--against <value>]

ARGUMENTS
  [PATH]  Path to snippets directory (overrides project config)

FLAGS
  --against=<value>  Compare the primary environment against this second environment instead of against local files
  --env=<value>      Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Show what differs in snippets between your local files and a WordPress environment, or between two environments

EXAMPLES
  $ lps snippet diff

  $ lps snippet diff --env staging

  $ lps snippet diff --env staging --against production

See code: src/commands/snippet/diff.ts

`lps snippet list`

List snippets from WordPress

USAGE
  $ lps snippet list [--json] [--env <value>]

FLAGS
  --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  List snippets from WordPress

EXAMPLES
  $ lps snippet list

See code: src/commands/snippet/list.ts

`lps snippet publish [PATH]`

Publish snippets to your Loopress account so they can be deployed to other projects. Does not touch any WordPress site.

USAGE
  $ lps snippet publish [PATH]

ARGUMENTS
  [PATH]  Path to snippets directory (overrides project config)

DESCRIPTION
  Publish snippets to your Loopress account so they can be deployed to other projects. Does not touch any WordPress
  site.

EXAMPLES
  $ lps snippet publish

  $ lps snippet publish --path ./snippets

See code: src/commands/snippet/publish.ts

`lps snippet pull [PATH]`

Pull snippets from WordPress

USAGE
  $ lps snippet pull [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to snippets directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Pull snippets from WordPress

EXAMPLES
  $ lps snippet pull

  $ lps snippet pull --path ./snippets

See code: src/commands/snippet/pull.ts

`lps snippet push [PATH]`

Push snippets to WordPress. Local snippet files created or updated remotely are renamed on disk to the <id>-<slug> convention.

USAGE
  $ lps snippet push [PATH] [--json] [--env <value>] [-d] [-y]

ARGUMENTS
  [PATH]  Path to snippets directory (overrides project config)

FLAGS
  -d, --dry-run      Show what would change without making changes
  -y, --yes          Answer yes to confirmation prompts
      --env=<value>  Target environment by name, overriding the globally active one (lps project switch)

GLOBAL FLAGS
  --json  Format output as json.

DESCRIPTION
  Push snippets to WordPress. Local snippet files created or updated remotely are renamed on disk to the `<id>-<slug>`
  convention.

EXAMPLES
  $ lps snippet push

  $ lps snippet push --path ./snippets

See code: src/commands/snippet/push.ts

`lps snippet rollback [PATH]`

Restore snippets to a snapshot taken automatically before an earlier lps snippet push

USAGE
  $ lps snippet rollback [PATH] [--json] [--env <value>] [-d] [-y] [--list] [--to <value>]

ARGUMENTS
  [PATH]  Path to snippets directory (overrides project config)

FLAGS
  -d, --dry-run

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme

Loopress

Usage

Error reporting

Commands

lps acf diff [PATH]

lps acf list

lps acf pull [PATH]

lps acf push [PATH]

lps acf rollback [PATH]

lps api diff [PATH]

lps api list

lps api publish [PATH]

lps api pull [PATH]

lps api push [PATH]

lps api rm FILENAME

lps api rollback [PATH]

lps app list

lps app pull [PATH]

lps app push [NAME]

lps app remove NAME

lps composer init

lps composer pull

lps composer push

lps dev

lps diff

lps doctor

lps form diff [PATH]

lps form list

lps form pull [PATH]

lps form push [PATH]

lps form rollback [PATH]

lps help [COMMAND]

lps hook diff [PATH]

lps hook list

lps hook pull [PATH]

lps hook push [PATH]

lps hook rm FILENAME

lps hook rollback [PATH]

lps init

lps login

lps logout

lps menu diff [PATH]

lps menu list

lps menu pull [PATH]

lps menu push [PATH]

lps menu rollback [PATH]

lps option add NAME

lps option diff [PATH]

lps option list

lps option pull [PATH]

lps option push [PATH]

lps option remove NAME

lps option rollback [PATH]

lps plugin add SLUG

lps plugin audit

lps plugin pull

lps plugin push

lps plugin status

lps project config

lps project list

lps project pull

lps project push

lps project remove

lps project rotate

lps project switch

lps promote FROM TO

lps pull

lps push

lps seo diff [PATH]

lps seo list

lps seo pull [PATH]

lps seo push [PATH]

lps seo rollback [PATH]

lps snippet diff [PATH]