[英]Migrating an EAR application from AppEngine to Google Cloud SDK
Since App Engine reached the end of life last August on the 30th, it's not possible anymore to deploy updates to the same application using the appengine ( appcfg
) command line.自去年 8 月 30 日 App Engine 生命周期结束以来,不再可能使用 appengine (
appcfg
) 命令行将更新部署到同一应用程序。
I was using the appengine maven plugin which in turn was using appcfg to deploy my application.我使用的是 appengine maven 插件,它又使用 appcfg 来部署我的应用程序。
I'm looking on how to migrate my application to Google Cloud SDK now but between the limitations I saw that Google Cloud SDK does not support EAR applications to be deployed.我现在正在研究如何将我的应用程序迁移到 Google Cloud SDK,但在我看到 Google Cloud SDK 不支持部署 EAR 应用程序的限制之间。
Surprize surprize my applications does have an EAR structure.令我惊讶的是,我的应用程序确实具有 EAR 结构。
Is there a workaround for this or should I completely change the structure of my application?是否有解决方法,或者我应该完全改变我的应用程序的结构?
You don't have to change your application structure at all.您根本不必更改应用程序结构。 It's only the deployment that it slightly altered.
它只是稍微改变了部署。
Before, you used to create war artifacts and package them into a deployable ear.以前,您曾经创建战争工件并将它们 package 放入可部署的耳朵中。
Now you keep creating the same war artifacts but you must not package them into an ear.现在你一直在创造同样的战争文物,但你不能把它们 package 放进耳朵里。 Instead, you deploy them all together using the gcloud command:
相反,您可以使用 gcloud 命令将它们全部部署在一起:
gcloud app deploy./path_module1/WEB-INF/appengine-web.xml./path_module2/WEB-INF/appengine-web.xml gcloud app deploy./path_module1/WEB-INF/appengine-web.xml./path_module2/WEB-INF/appengine-web.xml
path_moduleX are paths to the exploded artifacts (not path to your source code, of course) path_moduleX 是分解工件的路径(当然不是源代码的路径)
as explained here https://cloud.google.com/appengine/docs/standard/java/configuration-files如此处所述https://cloud.google.com/appengine/docs/standard/java/configuration-files
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.