It all depends on what you want to do - in some cases it is preferable to have Apache HTTP as the first point of entry for user requests. Reasons include performance - Apache HTTP servers up the static content - or security - Apache HTTP acts as a reverse proxy in a SSO setup.
If this is your production deployment, I would not advise running Tomcat using the Cargo plugin as provided with AppFuse. Far better would be to get Cargo or the Tomcat plugin to deploy to a container installed properly on the server. Mike. On 7/17/07, Aled Rhys Jones <[EMAIL PROTECTED]> wrote:
Ok cool. So if I get my app fuse project onto the remote server, install maven (java's on already) then run mvn -Dcargo.wait=true then I should be able to reach my app on port 8080 on the remote machine? Do I have to do any thing to get it working with Apache http? Thanks for your help Aled ------------------------------ *From:* Michael Horwitz [mailto:[EMAIL PROTECTED] *Sent:* 17 July 2007 08:38 *To:* [email protected] *Subject:* Re: [appfuse-user] Deploying to a linux box It is no different to Windows - one of the joys of Java! Simply install Java (if not installed already - just check that it is 1.5.x) and Maven and you are done. Mike On 7/16/07, *Aled Rhys Jones* <[EMAIL PROTECTED]> wrote: Hi all I've got a linux box with red hat enterprise 4 that I need to get my appfuse project running on. It currently has MySQL and Apache Httpd 2. What's the best course to follow in getting my build (currently running on windows) up and running on the linux box? Is it possible to use maven? I'd like to keep the Apache httpd functionality in order to serve other static apps if possible. If anyone could point me in the right direction it'd be much appreciated. The linux box is essentially a blank slate. I've got root access. Cheers Aled --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
