I am using Akeeba unite to restore backups from my staging server to my production server. My production server is running IIS. When UNITE runs it is copying over an .htaccess file that my IIS server blissfully ignores as it only cares about web.config files. Is there a way to get UNITE to write out a web.config file to limit access to the site white the backup is being performed? Ideally i would like the web.config file to redirect all users to an 'under maintenance page'.
#29587 Akeeba Unite and Stealth mode webconfig IIS
Posted in ‘UNiTE and Remote CLI’
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Environment Information
PHP version
n/a
Tool
UNiTE
Tool version
n/a
Latest post by dave.hook on Wednesday, 25 April 2018 10:45 CDT
Wednesday, 25 April 2018 09:09 CDT
dave.hook
Wednesday, 25 April 2018 09:39 CDT
nicholas
Akeeba Staff
Manager
Neither Kickstart nor UNiTE can write a web.config file. I have had mixed success with it, since some servers seem to require the site to be reloaded on IIS for the web.config to take effect. If you are sure that web.config files take immediate effect on your server I recommend that you wrap the restoration in a BAT or PowerShell script which writes the web.config file before restoration. At the end of the restoration you can delete the file.
If your original site has a web.config file, however, you must not delete the web.config file at the end of the restoration! The last step taken by UNiTE is to restore the original site's web.config file, if such a file did indeed exist at backup time. Therefore in this case the web.config file at the end of the restoration is not the stealth file you wrote with your script, it's the real site's web.config file which should remain intact.
I hope this information helps!
If your original site has a web.config file, however, you must not delete the web.config file at the end of the restoration! The last step taken by UNiTE is to restore the original site's web.config file, if such a file did indeed exist at backup time. Therefore in this case the web.config file at the end of the restoration is not the stealth file you wrote with your script, it's the real site's web.config file which should remain intact.
I hope this information helps!
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Wednesday, 25 April 2018 10:45 CDT
dave.hook
Thanks for the quick reply. I was thinking the same thing (using a batch file to swap out the web.config file) I was just hoping that Unite might be able to do it.
chris
chris