Upload on save

Every file you save in a site's local folder can go straight to a server, usually the Testing server, so a staging copy follows your edits.

Turning it on

1. Open Site Settings for the site.
2. Edit the server, for example Staging, and on its Advanced tab check Upload on save.
3. Save the site.

Each server has its own switch, so a site can push to its Testing server on save while its Remote server waits for Synchronize. Making Staging the Testing server in the servers table records which server it is for.

What happens on save

• The saved file is put to every server of its site whose Upload on save is on, 300 milliseconds after the last save, so a burst of saves puts it once.
• It goes through the same plan and guards as Put. A file changed on the server too since the last sync is not overwritten: a notification says so, and Synchronize lets you choose.
• A successful upload shows in the status bar for a moment, such as Put index.html to Staging, and in the log. A failure shows as an error with Show Log.

What is never uploaded on save

• Cloaked files and files inside cloaked folders.
• Files that match a sensitive pattern, such as .env or a private key. Put them with Synchronize, where you can check them on purpose.
• Anything, in a workspace in Restricted Mode. Trusting the workspace turns it back on.
• Anything, while the setting syncServers.uploadOnSave.enabled is off. It is the one switch over every server's Upload on save.

The log says why each file was held back, such as Not uploaded on save: it is cloaked.