Forgetting changed assets between releases
CLI
Stop uploading frontend assets manually
Use Smooth CDN CLI to publish optimized frontend assets directly from your terminal or CI/CD pipeline. Upload, version and deploy assets automatically while keeping stable CDN URLs.
A typical production release becomes a repeatable command instead of a manual checklist.
Example release flow
scdn create-version 1.2.1
scdn push
scdn publish-version 1.2.1
✓ DONE
Manual asset uploads do not scale
Asset deployment starts simple, then becomes a release risk as projects, files, and environments grow. Smooth CDN CLI turns those file tasks into one repeatable deployment step.
Inconsistent production asset sets
Uploading through dashboards before deploys
Deployment scripts growing around file handling
Keeping CDN assets in sync with application builds
From build output to published asset version
The CLI is one interface to the Smooth CDN workflow. Your build stays the same; asset publishing becomes part of the release.
Build frontend
Your existing build creates static assets.
Upload changes
The CLI sends changed build output to Smooth CDN.
Optimize automatically
Smooth CDN prepares lighter assets for delivery.
Publish version
The release becomes a named asset version.
Keep URLs stable
Your app keeps using stable CDN URLs.
What the deployment workflow gives you
Smooth CDN CLI is the fastest way for developers to use the platform's automated asset workflow from local terminals and deployment jobs.
Push build output
Send your entire build output to Smooth CDN without manual uploads.
Publish versions
Create predictable production releases with named asset versions.
Automate CI/CD
Use the same deployment flow locally and inside GitHub Actions, GitLab CI, or any release pipeline.
Keep URLs stable
Deploy new optimized assets without changing asset references across your application.
Sync changes safely
Replace manual dashboard uploads with repeatable deployments.
Built for deployment pipelines
Use Smooth CDN CLI when frontend assets need to move with the same discipline as application releases.
Frontend developers
Next.js projects
React projects
Static site generators
Teams using GitHub Actions
GitLab CI
Bitbucket Pipelines
Azure Pipelines
Custom deployment scripts
Why teams switch to the CLI
Manual uploads are fine for occasional files. They become a bottleneck when every production release needs the same asset set, version, and deployment result.
| Dashboard upload | Smooth CDN CLI |
|---|---|
| Upload files one by one | Push the whole build output |
| Easy to forget changed files | Repeatable commands for every release |
| Manual step before production | Runs inside CI/CD |
| No clear release package | Works with versioned asset packages |
Add Smooth CDN to your deployment pipeline
Install globally via npm:
npm install -g @smoothcdn/cliOr use it inside your project:
npm install @smoothcdn/cliAfter installation, sign in and initialize a project:
scdn login
scdn initFAQ
Does Smooth CDN CLI work only with Smooth CDN?+
Yes. It is the command-line client for Smooth CDN projects, assets, versions, and deployment flows.
Can I use it in CI/CD?+
Yes. Use an API key in GitHub Actions, GitLab CI, Bitbucket Pipelines, or custom release jobs.
Can I switch between asset versions?+
Yes. You can publish assets as named versions and mark the active version as latest. Older version URLs can stay available while new releases roll out.
Need exact command flags? Open the CLI docs.
Automate frontend asset deployment
Stop uploading assets manually. Publish optimized frontend assets from every release.