The Sentilis CLI publishes Markdown from your terminal. It works with any editor and fits scripts and CI. This guide covers the commands you will use most. See the CLI repository for the full reference.
Install and log in
npm i -g @sentilis/cli
sentilis auth login <your-token>Get your token from your Sentilis account. To check which profile is active:
sentilis auth whoamiSync a whole folder
sync validates and publishes every entry under a folder in one run:
sentilis sync ./my-contentThe folder follows the Sentilis layout: press/ for posts and docs, bio/ for your profile page, market/ for products and services, prime/ for memberships and gallery/ for visual work.
Two flags change how it behaves:
| Flag | What it does |
|---|---|
--dry-run | Validates everything without uploading. |
--strict | If any entry has validation issues, aborts the whole run without publishing anything. |
Use --dry-run while you write and --strict in CI.
Work with one entry
Each content type has its own commands for publishing and managing single entries:
sentilis press push ./press/my-post
sentilis press list
sentilis press info <entry>
sentilis press remove <entry>bio, market, prime and gallery follow the same pattern, with a few extras — for example market attach uploads a private attachment to an existing product.
Several profiles
If you publish to more than one profile, log in to each and pick one per command with --profile (or -p):
sentilis auth profiles
sentilis sync ./es --profile <profile>sentilis auth logout removes the active profile; --all removes every saved profile.
A typical session
sentilis sync ./my-content --dry-run # check
sentilis sync ./my-content # publish
sentilis press list # confirmIn CI
The same commands run in any CI system. See publishing with GitHub Actions for a complete workflow.