Editor

Manage who can sign in to the admin bar of a CMS the app hosts.

Syntax

$ vela cms editor add <email>
$ vela cms editor password <email> <password>
$ vela cms editor list

An app that hosts the backend signs editors in against the CMS’s own table, which starts empty and has no UI to fill it. These commands are how an editor gets an account. They open the same database the app uses, data/cms.sqlite at the project root, through the project’s own copy of @velastack/cms, so they need vela enable cms to have run first.

A CMS hosted on velastack.dev manages its own editors; these commands do not apply to it.

add

$ vela cms editor add you@example.com

Creates the editor. The password is generated and shown once; copy it before closing the terminal. Then run vela dev, open any page with ?edit on the URL (or press Ctrl+E), and sign in.

• --password <password> - Set the password instead of generating one
• --project <id> - Project the editor may edit, defaults to default, the id a single-tenant CMS resolves every request to

password

$ vela cms editor password you@example.com <password>

Sets a new password. Every session the editor has open is signed out, so they sign in again with the new one.

list

$ vela cms editor list

Shows every editor and the projects each may edit.