Redo Page

Redo CLI

Work on your site from the terminal.

The CLI pulls your site into a local .redo folder. Page-owned files live with the page. Shared blocks live in .redo/blocks and only push when you ask for them.

npm install -g @redopage/cli
redo login
redo init
redo whoami
redo pull page 1
redo dev
redo push page 1

The short story

Redo stays online. Your edits happen in local files. The CLI moves work both ways.

Redo site
  ↓ pull
.redo folder
  ↓ edit
Redo site
  ↑ push

How it works

1

Log in

The browser asks you to approve the CLI. Auth is stored globally.

2

Link a folder

Run init once so this folder points at one Redo site.

3

Pull files

Page-owned files live under pages. Shared blocks live under blocks.

4

Push edits

Page pushes avoid shared blocks unless you push them explicitly.

What you can do

  • List pages and blocks.
  • Read site content.
  • Pull page-owned files to .redo/pages.
  • Run a local preview.
  • Push page edits without accidentally pushing shared blocks.
  • Upload media.
  • Update site name, favicon, domain, and routing.
  • Publish when the site is ready.

Two command names

redo is the main command. cms is the same CLI with a short name.

redo --help
cms --help

Safety

Tokens stay global

redo init writes a project link. It does not put auth tokens in .redo/config.json.

Pull with care

redo pull writes files in .redo. Save your work before you pull again.

Delete asks first

redo delete asks before it deletes. Scripts must pass --yes.

Need more?

The full docs explain each command group.

Read CLI docs