Well... there might be some scenarios where it is still useful to put the site into maintenance mode as part of your deployment process.
Mahara's "site down for upgrade" message only shows when there is an upgrade to the Mahara core database version. However, it could be useful to put the site into maintenance mode if you are deploying other changes as well. For instance, you might be changing a theme, or rolling out a change that does not include a database change, but only changes to .tpl and .php files. In those cases, switching the site into maintenance mode would still be a good idea to keep users from having an inconsistent experience during the upgrade and any follow-up smoke testing. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1517279 Title: CLI tool for maintenance mode Status in Mahara: New Bug description: I would like the ability to enter and exit from maintenance mode from the command line. ...because we automate our deployments, and currently, we have php code embedded inside a shell script to accomplish entering and exiting from maintenance mode. This is really ugly. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1517279/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
