Support

As an update to ticket #29587 what I did to move my Joomla site that I am running on IIS offline during the Akeeba Unite restoration process. I am doing it this way because Akeeba Unite doesn't support writing a web.config file and even it it did, i would need to restart the production site for the new web.config to take effect. Also web.config isn't as friendly at the .htaccess so crafting a file that will allow only the localhost to access the site and force everyone else to a maintenance page isn't as simple as it is in .htaccess. What i am doing to get around this is as follows:

• My Akeeba Unite is being triggered nightly by a Task Scheduler Script.

• I created a new site on the IIS server called maintenance and added the same bindings as my production website. It will complain that only one site can be online at a time if they have the same bindings. Click OK.

• The new maintenance website only has one page called index.html which states we are down for maintenance and will be back soon.

• I added in new steps into the nightly Task scheduler script to take my production site offline and bring the maintenance site online, then run the restoration via UNiTE and then turn off the maintenance site and bring my production site back online. The commands are:

this code shuts down my production site

C:\Windows\System32\inetserv\appcmd.exe stop site production

this code starts up the maintenance site

C:\Windows\System32\inetserv\appcmd.exe start site maintenance

I then run the command to restore my site using Akeeba Unite

this code shuts the maintenance site down

C:\Windows\System32\inetserv\appcmd.exe stop site maintenance

this code starts the production site back up

C:\Windows\System32\inetserv\appcmd.exe start site production

I hope this helps others who are running IIS and want to hide the ANGIE site restoration pages from users while the site is being restored.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.