https://github.com/mike-ensor/first-cloud-app

Spring 3.1 and CloudFoundry with MongoDB
https://github.com/mike-ensor/first-cloud-app

Last synced: 5 months ago
JSON representation

Spring 3.1 and CloudFoundry with MongoDB

• Host: GitHub
• URL: https://github.com/mike-ensor/first-cloud-app
• Owner: mike-ensor
• Created: 2011-12-04T05:31:53.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2012-04-02T18:31:17.000Z (about 14 years ago)
• Last Synced: 2024-04-17T10:46:43.923Z (about 2 years ago)
• Language: Java
• Homepage: http://mikeensor.cloudfoundry.com/home
• Size: 211 KB
• Stars: 3
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

README

          
## How to run ##

To run this application, you must have Maven 3 and JDK 1.6+ installed and working AND MongoDB 1.8+ running locally for the tests to run

To run, type:

mvn clean package cargo:run

There are enhancements you can add to this configuration, like using JRebel and adding remote debugging. To enable both JRebel and remote debugging, simply add a profile in your settings.xml file:

...

...

    tomcat

    

        ${project.basedir}

        -noverify -javaagent:${env.REBEL_HOME}/jrebel.jar -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n

    

...

...

    tomcat

    ...

    ...

...

...

Reasoning behind using Cargo + Tomcat 7

The reason for tomcat 7 is to better replicate the production environment of many companies.  Typically the artifact of a build is a WAR, which is then deployed to Tomcat. One good way of doing this is to publish your WAR file to a repository like Artifactory, Nexus or Apache Artifact Repository.  During your deployment phase the artifact can be pulled from the repository.  This configuration is set up to replicate most of that configuration.