{"id":38290,"date":"2016-07-29T18:47:13","date_gmt":"2016-07-29T13:17:13","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=38290"},"modified":"2016-08-01T11:59:45","modified_gmt":"2016-08-01T06:29:45","slug":"run-grails-application-as-standalone-application","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/run-grails-application-as-standalone-application\/","title":{"rendered":"Run Grails application as standalone application"},"content":{"rendered":"

Most Grails application<\/a> are intended to deploy within external container.\u00a0According to the traditional way of deployment, the apps are bundled as war packaging, deploy it into any external container like tomcat and Jetty.<\/p>\n

There is a plugin Standalone App Runner<\/a> which allow to em-bade a container inside the grails application itself. The advantage of that is that a\u00a0Gails application can be run as a standalone application , without any dependency of external container.<\/p>\n

The embadded container comes up with application up and stop when we stop the application. To use this add the plugin dependencies in BuildConfig.groovy<\/p>\n

[java]
\ncompile "org.grails.plugins:standalone:9.0.0.M4"
\n[\/java]<\/p>\n

To create the Jar file with embadded container :<\/p>\n

[java]
\ngrails build-standalone
\n[\/java]<\/p>\n

To Run the Jar file as a stand alone application :<\/p>\n

[java]
\njava -jar \/path\/to\/jar_name.jar
\n[\/java]<\/p>\n

We can also pass the environment variables while running the jar to run the container with a specific environment configuration :<\/p>\n

[java]
\ngrails -Dgrails.env=prod build-standalone jar_name.jar
\n[\/java]<\/p>\n

This plugin has both Tomcat and Jetty container functionality, we can set the jetty as a default container. For that we need to specify that in BuildConfig.groovy :<\/p>\n

[java]
\ngrails.plugin.standalone.useJetty = true
\n[\/java]<\/p>\n

Also it can bs specify at the time of deployment which server will be used to run the application. we can specify the flag values for perticular container.<\/p>\n

[java]
\ngrails build-standalone –tomcat
\ngrails build-standalone –jetty
\n[\/java]<\/p>\n

It removes the external container dependency and easily integrate with the application. And the Grails application can be run as standalone application with Jar packaging.<\/p>\n

Hope this helps \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Most Grails application are intended to deploy within external container.\u00a0According to the traditional way of deployment, the apps are bundled as war packaging, deploy it into any external container like tomcat and Jetty. There is a plugin Standalone App Runner which allow to em-bade a container inside the grails application itself. The advantage of that […]<\/p>\n","protected":false},"author":203,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":11,"footnotes":""},"categories":[7,1],"tags":[4840],"class_list":["post-38290","post","type-post","status-publish","format-standard","hentry","category-grails","category-technology","tag-grails"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t