Our dev environment can be used in two ways Docker or Local Installation
Docker creates OS-level virtualization which allows it to function in it own contained environment and does not touch any of your computer files. The local installation does touch some of our your computers own files, but you get the benefit of speed. Since Docker always creates a new container each time you run a command it is naturally slower than if you run the commands without virtualization and locally stored caches.
We set up our Docker environment to be easy to work with. When you start the container it will start a process that listens for change under your classpath, once a change is detected it will automatically rebuild the changed files and restart the servlet container (in our case Tomcat). This allows a simple and easy development process because you never have to rebuild manually, the container knows what it needs to do and it does it for you.
To use Docker, follow these steps:
docker-compose up -dhttp://localhost:8080/ in your browser to see the application running.If you want to run tests it's as easy as
docker-compose run gradle testIf you want to do test driven development you can run
docker-compose run gradle -t testthe -t watches for changes and runs the same command again when a change happens.
NOTE: The first time you run the docker-compose command it will take a bit longer to start so be patient
NOTE: We don't recommend the local installation unless you have worked with Gradle and/or other JVM-based languages before.
The local installation offers more control and more configuration for your own development environment, but we update the Java versions without warning so make sure to keep your local environment up to date and check this guide periodically so you can migrate to the new requirements.
To install locally, follow these steps:
./gradlew bootRunhttp://localhost:8080/ in your browser to see the application runningIf you want to run tests it's as easy as ./gradlew test. If you want to do test driven development you can run ./gradlew -t test
the -t watches for changes and runs the same command again when a change happens.
Once everything is working, and you have navigated to http://localhost:8080/ you should see the root API resource in a hal+json format. If you don't see that check the troubleshooting section.
When docker-entrypoint.sh runs it will output two log files spring-build.log and spring-run.log (we recommend running
tail -f on these files for a more detailed output).
The logs will give you more information about what is going on inside the application.
spring-build.log informs you in case you have any compile-time errors happening in your code such as syntax or type errors,
missing dependencies, etc.spring-run.log informs you about the runtime errors such as webserver exceptions, and the Tomcat access log.If you are having any issues setting up odds are one of these two files will tell you what you need to do.
We have added JVM args to the bootRun task. These JVM args enable something called JPDA (Java Platform Debugger Architecture)
this allows you to add breakpoints in your code witch get triggered when that part of the code executes.
(Check the documentation for your code editor or IDE for more information about how to set up JPDA).
These are the JVM args we used to enable JPDA:
-Xdebug -Xrunjdwp:transport=dt_socket,address=*:5005,server=y,suspend=nFor further reference, please consider the following sections:
The following guides illustrate how to use some features concretely:
These additional references should also help you: