Michael Conneen wrote:
I looked at the forrestbot for about 1 minute.. then spent another
minute using a maven task. It's a hammer thing I guess.. the problem
looked like a nail! :)
Yeah, the forrestbot does do much more than just deploy the content. You
can do stuff like staging the content
I looked at the forrestbot for about 1 minute.. then spent another
minute using a maven task. It's a hammer thing I guess.. the problem
looked like a nail! :)
Kind Regards,
Michael L. Conneen
Information Integrators, Inc.
http://www.infointegrators.com
PGP Key: http://mconneen.infointegrators
Michael Conneen wrote:
For high-traffic sites, we also cron/schedule a "forrest site" and a
maven task to deploy it.The schedule varies depending on the site.
Some are done every 15 minutes.. some nightly.
You probably want to consider using the forrestbot to do that, it's what
we built
Johannes Schaefer wrote:
So, there are some options to run Forrest in live mode:
1. 'forrest run': runs Jetty in a console window (stays open in Windows)
2. 'forrest war': creates a web application to deploy e.g. in tomcat
a) use the webapp directory
b) use "context descriptors" to use ano
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have been doing option 2b for over 1+ years. There have been some
anomalies, like pages not reloading... but these were several versions
of Forrest ago.
For high-traffic sites, we also cron/schedule a "forrest site" and a
maven task to deploy i
So, there are some options to run Forrest in live mode:
1. 'forrest run': runs Jetty in a console window (stays open in Windows)
2. 'forrest war': creates a web application to deploy e.g. in tomcat
a) use the webapp directory
b) use "context descriptors" to use another webapp directory
c)
