Apply an approved change over FTP or SFTP
For servers without a repository — with a backup taken before every write.
Some sites are edited on the server rather than through a repository. For those, an approved fix can be written directly — always behind an approval, and always after a backup.
This writes to a live server. Set it up on staging first and confirm the revert works before you connect anything that customers depend on.
Connect a server
- Open Project → Edit → Deployment.
- Choose FTP or SFTP and enter the host, port, username, password, and remote path.
- Press Test connection — it lists the remote directory so you can confirm the path is right.
Credentials are encrypted before storage and masked in every API response.
The approval flow
| State | What it means |
|---|---|
| none | No change has been proposed for this incident |
| pending | A change is waiting for a human decision |
| approved | Someone approved it; it has not been written yet |
| applied | The file was written and a backup was stored |
| reverted | The backup was restored |
| failed | The write did not complete — the reason is recorded |
The approver and the timestamps are stored with the analysis, so months later you can still answer who approved what.
Reverting
Open the incident and press Revert. The backup taken before the write is restored and the state moves to reverted.
A backup is not a guarantee. It restores the file that was changed — not a database migration, a cache, or anything else the change set in motion.