Proposition 4 seems probably the best way to do this. Some structures have a โmaintenance modeโ in which all incoming requests will be redirected to a page indicating that the site is down due to maintenance. If your infrastructure does not support this mode, you can simply download the new version of your application (perhaps call the maintenance version) and switch to it as your new default version. This version may be a blank application, in which all incoming requests go to the service page, indicating that the site is not working for maintenance. Then manually go to the version of your application with the migration code and execute it ( http://<version>.<appname>.appspot.com ). Switch the version of your default version to the new version with a new scheme when you are done with the migration.
Explain your other ideas.
- Disabling recording may prevent you from even recording in the application. I believe that this was more intended to move from one application to another or to other data warehouse freeze applications.
- Disable application will completely disable the application.
- Redirecting your domain will delay the DNS in your migration, which may take 48 hours to fully distribute each method (switching to a temporary page and then switching to a new version).
- As already mentioned, IMHO is the best way to do this.
source share