blodemd push
Deploy documentation to Blode.md.
Upload your documentation files and publish them to Blode.md in a single command.
blodemd push [dir]If you omit the dir argument, the CLI searches for a docs.json file in these locations (in order):
./docs./apps/docsIf none contain a docs.json, the current directory is used.
When you run blodemd push, the CLI executes these steps:
Reads and parses docs.json from the resolved docs directory.
Recursively collects all files in the directory. Dotfiles and node_modules
are skipped automatically.
Sends a request to the Blode.md API to create a new deployment record with the branch and commit message.
Uploads files in batches of up to 4 MB each. Large documentation sets are split across multiple requests.
Marks the deployment as complete and promotes it to production. Your docs are live immediately.
If the project slug does not match an existing project, the CLI prompts you to create one. This requires an OAuth session (from blodemd login), not just an API key.
When a project is created, the CLI prints an API key you can use for CI/CD deployments.
API key authentication cannot auto-create projects. You need to run blodemd login first, or create the project from the dashboard.
blodemd pushThe CLI skips the following entries during file collection:
. (dotfiles)node_modules directory