• Enable python with mod-wsgi: http://www.howtoforge.com/forums/showthread.php?t=24109
  • mod-python is an embedded python intepreter. mod-cgi invokes external intepreters, which may run as different user than www-root. So more security added. mod-wsgi is like mod-cgi but more resource-friendly on production server.
  • mod-proxy to redirect requests to JavaEE Server.

mod_python is the closest equivalent of mod_php, but this doesn't mean that mod_python will suit your needs. For each programming language you have to enumerate all the possible options and choose the one you'll need.

For PHP, you have mod_php and mod_cgi, but from this two mod_cgi is inferior in almost all ways to mod_php so people usually choose the latter. (There are some alternatives, like suphp if you need more security, etc.)

For Python you have mod_cgi, which will run the python interpreter each time you make a request. Mod_python instead has python embedded so it's usually faster and simpler to do, but for large projects, or projects that are using a framework (like DJango) you will probably want to use mod_wsgi because it is the most resource-friendly.

For ruby you also have the option to use mod_cgi, but that will be way too slow. mod_ruby is also an option, but only for small programs. mod_fastcgi was usually the option for rails/merb and other ruby based web frameworks, but they are superseeded by mod_rails and mod_rack, which are esource-friendly. But for simple scripts the latter are a bit too heavy-weight.

For mono (asp.net) you have mod_mono, which is usually the only option.

For java you usually run a separate Tomcat/Jetty web server, and use mod_proxy.

Of course running a separate web server and use mod_proxy is usually an option for all the web frameworks, although it is mostly suitable for the development process only. For production environments you have to choose carefuly the best option (the one which is the mostly resource-friendly) your framework (django,rails,asp.net,etc.) needs

• Setup apache2 proxy to jbossAS: http://ocpsoft.org/opensource/jboss-application-server-7-on-port-80-with-apache-httpd-proxypass/
  • http://www.outjected.com/blog/2012/12/13/another-mod-proxy-jboss-how-to.html

Setup reference:

• http://programmaticponderings.wordpress.com/2013/11/04/continuous-integration-and-deployment-using-git-maven-jenkins-and-glassfish/
• http://ars-codia.raphaelbauer.com/2013/09/jboss-arquillian-and-jenkins.html
• http://zeroturnaround.com/rebellabs/release-management-for-enterprises/
• http://www.infoq.com/articles/orch-pipelines-jenkins

• Development: notebook
• Git: bitbucket? visrc?
• Jenkin CI Server: dev-host, better in VM?
• Deployment
  • dev: host
  • Test: vm
  • Production: visrc.com netbook

• Jenkin CI with yum. Jenkin is auto-started on port 8080
• JbossAS 7.1
• Check out project on Eclipse

Firstly we setup development, test, production server on single host. We configure multiple jbossAS instances on one machine.

https://community.jboss.org/thread/221012

• cp -rp default development
• vim ~/development/configuration/standalone.xml

  <socket-binding-group name=“standard-sockets” default-interface=“public” port-offset=“${jboss.socket.binding.port-offset:10000}”

  >

    <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

  • create start script

      
      cat<< 'EOF' > development.sh; chomod +x development.sh
      standalone.sh -Djboss.server.base.dir=$(pwd)/../development -Dorg.jboss.boot.log.file=$(pwd)/../development/log/boot.log -Dlogging.configuration=$(pwd)/../development/configuration/logging.properties
      EOF

  • In eclipse, go to Window / Preferences / Server / Runtime Environments / Add

  C

  reate a runtime environment “JBoss 7.1 Runtime Development”.