You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Bilgin Ibryam <bi...@gmail.com> on 2016/11/06 22:46:54 UTC
Common way for deploying isis apps
Hi all,
I was wondering what is the most common way for running isis apps?
I know while developing I can use jetty plugin or the WebServer
classes, but what about for running it on other environments?
For my semat app I have used the .war file in a tomcat instance. And
ll that in a docker container.
You can see my pom.xml used for building docker container and running
at [1] and the demo app running at [2]
Also noticed that with tomcat 9 the app was throwing lot's of errors
with some not allowed cookie values, so moved back to tomcat 7.
Is anyone running isis w/o a web container, as standalone Java app?
How do you package the app in the case?
[1] https://github.com/bibryam/semat/blob/master/pom.xml
[2] http://semat.ofbizian.com/
Cheers,
--
Bilgin Ibryam
Camel Committer at ASF & Integration Architect at Red Hat
Blog: http://ofbizian.com | Twitter: @bibryam
Camel Design Patterns https://leanpub.com/camel-design-patterns
Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475
Re: Common way for deploying isis apps
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Even easier... 1.13.2.1 of the simpleapp archetype now has docker support.
If that's your thang. It's the way we're headed with Estatio, at least.
Cheers
Dan
On Wed, 9 Nov 2016 at 18:36 Óscar Bou - GOVERTIS <o....@govertis.com> wrote:
> Hi Willie.
>
> Really nice workflow.
>
> Could you contribute part of the CD/CI scripts that could be used/evolved
> by the community ?
>
> Thanks,
>
> Oscar
>
>
>
> > El 9 nov 2016, a las 18:24, Willie Loyd Tandingan <
> tandingan.wlb@gmail.com> escribió:
> >
> > We used to deploy using cargo to a remote Wildfly server. After several
> deployments, the web server will run out of heap space which is quite a
> common problem, and we would need to manually restart the server. On top of
> that, the reconfiguration for production happens at war assembly and we had
> no way to reconfigure the artifact for different environments.
> >
> > Right now, we have a setup where every time a commit is made to the
> repository, a builder machine will try to build, test, generate exploded
> war, copy to a base Wildfly docker image, and publish the built image to a
> private registry. It made life really easier.
> >
> > Cheers,
> > Willie
> >
> >> On 7 Nov 2016, at 6:46 AM, Bilgin Ibryam <bi...@gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I was wondering what is the most common way for running isis apps?
> >> I know while developing I can use jetty plugin or the WebServer
> >> classes, but what about for running it on other environments?
> >>
> >> For my semat app I have used the .war file in a tomcat instance. And
> >> ll that in a docker container.
> >> You can see my pom.xml used for building docker container and running
> >> at [1] and the demo app running at [2]
> >>
> >> Also noticed that with tomcat 9 the app was throwing lot's of errors
> >> with some not allowed cookie values, so moved back to tomcat 7.
> >>
> >> Is anyone running isis w/o a web container, as standalone Java app?
> >> How do you package the app in the case?
> >>
> >>
> >> [1] https://github.com/bibryam/semat/blob/master/pom.xml
> >> [2] http://semat.ofbizian.com/
> >>
> >> Cheers,
> >>
> >> --
> >> Bilgin Ibryam
> >> Camel Committer at ASF & Integration Architect at Red Hat
> >> Blog: http://ofbizian.com | Twitter: @bibryam
> >>
> >> Camel Design Patterns https://leanpub.com/camel-design-patterns
> >> Instant Apache Camel Message Routing
> http://www.amazon.com/dp/1783283475
>
>
>
>
Re: Common way for deploying isis apps
Posted by Óscar Bou - GOVERTIS <o....@govertis.com>.
Hi Willie.
Really nice workflow.
Could you contribute part of the CD/CI scripts that could be used/evolved by the community ?
Thanks,
Oscar
> El 9 nov 2016, a las 18:24, Willie Loyd Tandingan <ta...@gmail.com> escribió:
>
> We used to deploy using cargo to a remote Wildfly server. After several deployments, the web server will run out of heap space which is quite a common problem, and we would need to manually restart the server. On top of that, the reconfiguration for production happens at war assembly and we had no way to reconfigure the artifact for different environments.
>
> Right now, we have a setup where every time a commit is made to the repository, a builder machine will try to build, test, generate exploded war, copy to a base Wildfly docker image, and publish the built image to a private registry. It made life really easier.
>
> Cheers,
> Willie
>
>> On 7 Nov 2016, at 6:46 AM, Bilgin Ibryam <bi...@gmail.com> wrote:
>>
>> Hi all,
>>
>> I was wondering what is the most common way for running isis apps?
>> I know while developing I can use jetty plugin or the WebServer
>> classes, but what about for running it on other environments?
>>
>> For my semat app I have used the .war file in a tomcat instance. And
>> ll that in a docker container.
>> You can see my pom.xml used for building docker container and running
>> at [1] and the demo app running at [2]
>>
>> Also noticed that with tomcat 9 the app was throwing lot's of errors
>> with some not allowed cookie values, so moved back to tomcat 7.
>>
>> Is anyone running isis w/o a web container, as standalone Java app?
>> How do you package the app in the case?
>>
>>
>> [1] https://github.com/bibryam/semat/blob/master/pom.xml
>> [2] http://semat.ofbizian.com/
>>
>> Cheers,
>>
>> --
>> Bilgin Ibryam
>> Camel Committer at ASF & Integration Architect at Red Hat
>> Blog: http://ofbizian.com | Twitter: @bibryam
>>
>> Camel Design Patterns https://leanpub.com/camel-design-patterns
>> Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475
Re: Common way for deploying isis apps
Posted by Willie Loyd Tandingan <ta...@gmail.com>.
We used to deploy using cargo to a remote Wildfly server. After several deployments, the web server will run out of heap space which is quite a common problem, and we would need to manually restart the server. On top of that, the reconfiguration for production happens at war assembly and we had no way to reconfigure the artifact for different environments.
Right now, we have a setup where every time a commit is made to the repository, a builder machine will try to build, test, generate exploded war, copy to a base Wildfly docker image, and publish the built image to a private registry. It made life really easier.
Cheers,
Willie
> On 7 Nov 2016, at 6:46 AM, Bilgin Ibryam <bi...@gmail.com> wrote:
>
> Hi all,
>
> I was wondering what is the most common way for running isis apps?
> I know while developing I can use jetty plugin or the WebServer
> classes, but what about for running it on other environments?
>
> For my semat app I have used the .war file in a tomcat instance. And
> ll that in a docker container.
> You can see my pom.xml used for building docker container and running
> at [1] and the demo app running at [2]
>
> Also noticed that with tomcat 9 the app was throwing lot's of errors
> with some not allowed cookie values, so moved back to tomcat 7.
>
> Is anyone running isis w/o a web container, as standalone Java app?
> How do you package the app in the case?
>
>
> [1] https://github.com/bibryam/semat/blob/master/pom.xml
> [2] http://semat.ofbizian.com/
>
> Cheers,
>
> --
> Bilgin Ibryam
> Camel Committer at ASF & Integration Architect at Red Hat
> Blog: http://ofbizian.com | Twitter: @bibryam
>
> Camel Design Patterns https://leanpub.com/camel-design-patterns
> Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475
Re: Common way for deploying isis apps
Posted by Jeroen van der Wal <je...@stromboli.it>.
Hi Bilgin,
We are deploying the .war to Tomcat 8 instances. We are investigating
Docker and Fabric8 for our CD platform.
Cheers,
Jeroen
On 7 November 2016 at 11:23, Martin Grigorov <mg...@apache.org> wrote:
> Hi,
>
> Isis simpleapp (and any other demo app) has config for Jetty-Console:
>
> <plugin>
> <groupId>org.simplericity.jettyconsole</groupId>
> <artifactId>jetty-console-maven-plugin</artifactId>
> <executions>
> <execution>
> <goals>
> <goal>createconsole</goal>
> </goals>
> <configuration>
>
> <backgroundImage>${basedir}/src/main/jettyconsole/isis-
> banner.png</backgroundImage>
>
> <destinationFile>${project.build.directory}/${project.
> build.finalName}-jetty-console.jar</destinationFile>
> </configuration>
> <phase>package</phase>
> </execution>
> </executions>
> </plugin>
>
>
> This is handy to start the app from .jar.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Mon, Nov 7, 2016 at 6:58 AM, Kevin Meyer <ke...@kmz.co.za> wrote:
>
> > Hi,
> > I haven't tried in a while, but I used to use the shade plugin to create
> a
> > standalone jar.
> > Cheers,
> > Kevin
> >
> >
> > On 6 November 2016 23:46:54 CET, Bilgin Ibryam <bi...@gmail.com>
> wrote:
> > >Hi all,
> > >
> > >I was wondering what is the most common way for running isis apps?
> > >I know while developing I can use jetty plugin or the WebServer
> > >classes, but what about for running it on other environments?
> > >
> > >For my semat app I have used the .war file in a tomcat instance. And
> > >ll that in a docker container.
> > >You can see my pom.xml used for building docker container and running
> > >at [1] and the demo app running at [2]
> > >
> > >Also noticed that with tomcat 9 the app was throwing lot's of errors
> > >with some not allowed cookie values, so moved back to tomcat 7.
> > >
> > >Is anyone running isis w/o a web container, as standalone Java app?
> > >How do you package the app in the case?
> > >
> > >
> > >[1] https://github.com/bibryam/semat/blob/master/pom.xml
> > >[2] http://semat.ofbizian.com/
> > >
> > >Cheers,
> >
> > --
> > Sent from my phone with K-9 Mail.
> > Please excuse my brevity.
> >
>
Re: Common way for deploying isis apps
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
Isis simpleapp (and any other demo app) has config for Jetty-Console:
<plugin>
<groupId>org.simplericity.jettyconsole</groupId>
<artifactId>jetty-console-maven-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>createconsole</goal>
</goals>
<configuration>
<backgroundImage>${basedir}/src/main/jettyconsole/isis-banner.png</backgroundImage>
<destinationFile>${project.build.directory}/${project.build.finalName}-jetty-console.jar</destinationFile>
</configuration>
<phase>package</phase>
</execution>
</executions>
</plugin>
This is handy to start the app from .jar.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, Nov 7, 2016 at 6:58 AM, Kevin Meyer <ke...@kmz.co.za> wrote:
> Hi,
> I haven't tried in a while, but I used to use the shade plugin to create a
> standalone jar.
> Cheers,
> Kevin
>
>
> On 6 November 2016 23:46:54 CET, Bilgin Ibryam <bi...@gmail.com> wrote:
> >Hi all,
> >
> >I was wondering what is the most common way for running isis apps?
> >I know while developing I can use jetty plugin or the WebServer
> >classes, but what about for running it on other environments?
> >
> >For my semat app I have used the .war file in a tomcat instance. And
> >ll that in a docker container.
> >You can see my pom.xml used for building docker container and running
> >at [1] and the demo app running at [2]
> >
> >Also noticed that with tomcat 9 the app was throwing lot's of errors
> >with some not allowed cookie values, so moved back to tomcat 7.
> >
> >Is anyone running isis w/o a web container, as standalone Java app?
> >How do you package the app in the case?
> >
> >
> >[1] https://github.com/bibryam/semat/blob/master/pom.xml
> >[2] http://semat.ofbizian.com/
> >
> >Cheers,
>
> --
> Sent from my phone with K-9 Mail.
> Please excuse my brevity.
>
Re: Common way for deploying isis apps
Posted by Kevin Meyer <ke...@kmz.co.za>.
Hi,
I haven't tried in a while, but I used to use the shade plugin to create a standalone jar.
Cheers,
Kevin
On 6 November 2016 23:46:54 CET, Bilgin Ibryam <bi...@gmail.com> wrote:
>Hi all,
>
>I was wondering what is the most common way for running isis apps?
>I know while developing I can use jetty plugin or the WebServer
>classes, but what about for running it on other environments?
>
>For my semat app I have used the .war file in a tomcat instance. And
>ll that in a docker container.
>You can see my pom.xml used for building docker container and running
>at [1] and the demo app running at [2]
>
>Also noticed that with tomcat 9 the app was throwing lot's of errors
>with some not allowed cookie values, so moved back to tomcat 7.
>
>Is anyone running isis w/o a web container, as standalone Java app?
>How do you package the app in the case?
>
>
>[1] https://github.com/bibryam/semat/blob/master/pom.xml
>[2] http://semat.ofbizian.com/
>
>Cheers,
--
Sent from my phone with K-9 Mail.
Please excuse my brevity.