简单的方式在已部署的grails应用程序上创建补丁 [英] simple way to create patch on deployed grails application

问题描述

我在我的客户机服务器上的tomcat6上部署了grails应用程序，但该应用程序仍然需要很多修复，所以每个在客户端机器上创建或缺少功能的bug，我创建了一个补丁并通过ftp上的.tar .gz文件将替换已部署的文件夹。

我无法发送完整的.war文件，因为应用程序很大（〜80M），所以发送更改.class文件是我唯一的选择。但创建修补程序的过程太耗时，特别是在重建项目上，清理目标文件夹并开始编译项目中的所有文件。之后，我使用新的 target / classes 文件夹中的比较文件夹应用程序与旧的目标/类文件夹相比较，搜索不同的.class文件，然后将其发送给客户端。

创建战争过程确实需要很多时间才能解决一个小问题，是否有一种更简单的方法在编译代码上获得不同的.class ？因为我需要在2-3天内创建补丁程序，每个补丁程序都可以修复一些常规客户端报告的内容。

感谢，

解决方案

我们构建WAR文件，然后在本地解压缩并同步本地分解的WAR（使用 RSync ）与服务器上的分解WAR（在开发人员Windows机器上使用Cygwin）。 RSync协议非常高效，因此通过互联网进行部署非常快速，但WAR文件生成仍然需要大量时间:(

）

我们在开发者机器以及服务器上，所以我们的部署机制是非常简单的，如果你打折了WAR构建时间，并且我们不直接进入生产目录，我们等待rsync完成，然后在服务器，它也支持以前的生产版本，以防出现可怕的错误。

i have a deployed grails apps on tomcat6 in my client server machine, but the application is still need many fix, so every bug founded or missing feature on client machine, i creating a patch and delivering to client via ftp on .tar.gz file that will replace on deployed folder.

i can't send a fully .war files because the apps is big (~80M), so sending a changes .class files is the only option i have. but the process to creating a patch is too time consuming, especially on rebuild the project, cleaning up the target folder and start to compile all files on project. after that i search the different .class files using on comparison folder apps on new target/classes folder compared to old target/classes folder, and send it to client.

the creating war process is really took many time just to fix a minor thing, is there a way more simple to get a different .class on compiled code? because i need to create patch on 2-3days each for fixing a little stuff that also routinely client reported.

thanks,

解决方案

We build the WAR file, then unzip it locally and synchronize the locally exploded WAR (using RSync) with the exploded WAR on the server (using Cygwin on the developer Windows machines). The RSync protocol is very efficient so the deploy over the internet is very fast, but the WAR file generation still takes a lot of time :(

We have scripts on both the developer machines as well as on the server so our deploy mechanism is pretty painless, if you discount the WAR build time. Also, we don't rsync directly into the production directory, we wait until rsync is done and then run a script on the server which also backs up the previous production version in case something goes horribly wrong.

这篇关于简单的方式在已部署的grails应用程序上创建补丁的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！