Never test changes on a live site again. Kelma lets you create a staging copy, try plugin updates, theme changes, or new code safely, then push exactly what you want to production — all without touching the command line.
kelma
OverviewSettingsWordPressDatabasesBackupsTerminalSecurityCronRedirectsSSLDomainsMonitoringCollaborators
Push to live
Sync your staging copy to a live site.
yoursite.com▾
Push files
◉ All files ○ Selected folders
Push database
○ Entire database ◉ Selected tables (12/41)
Push to selected site
Create a staging site
- Go to Sites → New Site and choose the Staging type (a test site on a .kelma.io subdomain).
- Or clone an existing site so staging starts as an exact copy of production.
- Build and test freely — staging is isolated, so nothing you do touches your live visitors.
Tip: Use staging for every plugin or theme update. Confirm the site still works there, then push — your live site only ever sees changes that already passed the test.
Push to live
When your changes are ready, open Push to live and choose what to deploy:
- Pick the target site (your production site).
- Tick Push files — all files, or just selected folders like /wp-content.
- Tick Push database — the entire database, or selected tables only.
- Click Push to selected site. Caches are purged automatically on deploy.
URLs are rewritten on import. When you push the database, the staging URLs are rewritten to the target (production) domain automatically — so links and settings point to the right place.
Tips & tricks
- Push files only when you have changed a theme or plugin but do not want to overwrite live orders or content in the database.
- Push selected tables when you have edited options or a custom table on staging but production has newer orders you must keep.
- Snapshot production first. Take a temporary backup of the live site before a push, so a one-click rollback is ready if needed.
- Keep staging fresh. Re-clone from production before starting major work so you are testing against current data.
Leave a Reply