Server Management: Apache VHost Rebuilds Now Require Explicit Confirmation
Server Management no longer overwrites an Apache vhost file quietly. Saving a project's settings only rebuilds the vhost when something that affects it actually changed, and any rebuild now asks you first.
01 Saving no longer implies a rebuild
Previously, saving a project's settings could rebuild the vhost regardless of what you edited. Now the rebuild only happens when the hostname, the aliases, the project type or the path have actually changed. Editing anything else leaves the vhost file untouched.
Saving settings could rebuild the vhost silently, discarding manual customisations in the file.
The vhost is rebuilt only when hostname, aliases, type or path changed, and only after you confirm.
02 Explicit confirmation before anything is written
Both cases now ask for explicit confirmation: a save that would trigger a rebuild, and the “Create VHost” button. The prompt spells out what is at stake — any manual customisations in the existing vhost file will be lost.