Spring boot and react hot starter
image:https://travis-ci.org/geowarin/boot-react.svg?branch=master[“Build Status”, link=”https://travis-ci.org/geowarin/boot-react”] image:https://ci.appveyor.com/api/projects/status/y3uw0gpo9dtec349?svg=true[“Windows build Status”, link=”https://ci.appveyor.com/project/geowarin/boot-react”]
Be more productive with this simple project that uses the https://spring.io/blog/2015/06/17/devtools-in-spring-boot-1-3[spring dev tools] and https://github.com/gaearon/babel-plugin-react-transform[react transform] for hot reloading.
Everything: backend, frontend and styles will be hot reloaded automatically.
See http://geowarin.github.io/spring-boot-and-react-hot.html[my article] for an in-depth explanation.
This project also sets up spring security and http://projects.spring.io/spring-session/[spring-sessions], which will automatically store your sessions in Redis, allowing you to scale on multiple servers.
Both the frontend and the backend are fully tested.
The Java code is available in the
In development you will have access to the awesome https://github.com/gaearon/redux-devtools[redux-dev-tools], which will allow you keep track of your application state and undo/redo every action at will.
But… I love Groovy :‘(
Me too pal…
The project used to be coded in Groovy but since most of us use Java at work, I figured it would be more useful for a lot of people if the backend code was written in Java.
There is a https://github.com/geowarin/boot-react/tree/groovy[groovy branch] that should be up to date.
The tests are still http://geowarin.github.io/test-java-with-groovy.html[written in groovy].
Running the backend (recommended)
The recommended way to launch the server is to use your favorite java IDE.
The main method of the application is in the
Running the frontend (recommended)
For the frontend, a small wrapper script for UNIX systems can be found at the root of the project. It will ensure that you use the same version of npm as the gradle build.
./npmw start to start the frontend.
It will automatically run
npm install on the first run.
If you change the node dependencies in
package.json, delete the
node_modules dir or
Alternatives for running the projects
There is also a gradle task to run the spring server:
The node version used by the gradle build is specified https://github.com/geowarin/boot-react/blob/master/frontend/build.gradle#L11-L12[here]. If you have an equivalent version of npm installed on your system, you can use it to start the frontend.
Go in the
frontend directory and type
npm install to install the dependencies.
npm start to start the dev server.
You will need node 5.0+ and npm 3 to run the dev server and build the project
If you do not have the required binaries on your machine, you can use
./gradlew frontend:npmInstall and
Those two command will download the required node/npm versions automatically and use them to run the node tasks.
For the backend, recompiling the project in your IDE will trigger the reloading of the application’s class loader.
Sessions are stored in Redis with spring-sessions. Spring-sessions allows you to transparently persist the HttpSession on Redis. This allows to distribute the load on multiple servers if you choose to.
The application relies on a stateless REST api.
When they authenticate, clients will be given a token.
They will save this token in their local storage and send it as an HTTP header (
This allows the retrieval of the session data in Redis.
If you want to use a real redis, you can run the application with the
redis profile is not active, your session will be stored in a map.
This is great in development but you should avoid it in production.
| Profile | description | uses
redis | Use a real redis connecting on localhost by default. | Yes
!redis) | Uses a map to store sessions | Yes
If your run your project with gradle, the system properties won’t be passed on to Spring. See https://github.com/spring-projects/spring-boot/issues/832[this issue] for workarounds.
The simplest way to go is to specify active profiles in your IDE.
http://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-profiles.html[Check out the doc] to learn more about profiles in Spring Boot.
To run the jar in production mode use the following command:
java -jar boot-react-0.0.1-SNAPSHOT.jar --spring.profiles.active=production 16:57:01
The application is configured to work with Spring Security. It uses an in-memory authentication but you are free use http://docs.spring.io/spring-security/site/docs/4.0.2.RELEASE/reference/htmlsingle/#jc-authentication[other implementations] or to http://docs.spring.io/spring-security/site/docs/4.0.2.RELEASE/reference/htmlsingle/#core-services[roll your own].
This project uses https://github.com/rackt/react-redux[Redux] to handle state and actions. It is a simple library with very powerful dev tools.
Dan Abramov, the author of Redux, published a https://egghead.io/series/getting-started-with-redux[great Redux video tutorial].
I also suggest reading the https://github.com/rackt/react-redux/blob/master/docs/quick-start.md[redux quick start] to understand how to architecture you application and the difference between containers and components.
Components are simple display elements that receive everything they need (state and actions) via props.
Containers are connected to Redux and as such, they can pull whatever properties they are interested in from the state and bind actions to dispatch. Those containers are only connecting simple components to Redux.
Small components are written using the https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html#stateless-functional-components[stateless functional components syntax], i.e, those component are pure render components and only their props will have an impact on the DOM.
Beware, hot reloading is not supported on functional components yet (see https://github.com/geowarin/boot-react/issues/13[this issue]) unless they are wrapped in a real Component.
We can http://rackt.github.io/redux/docs/recipes/WritingTests.html[write tests] on connected components, but it is more effective to test them in isolation from Redux.
Router push state
The project uses https://github.com/rackt/react-router[react-router] to handle routes. You can choose several modes to handles the router history. By default, the project uses the browser history, which creates the nicest URLs (/login, /private, etc.).
In development, we use a dev server that https://github.com/geowarin/boot-react/blob/master/frontend/server.js#L21-L24[proxies] requests to the index.
In production, we have to use a special https://github.com/geowarin/boot-react/blob/master/backend/src/main/java/react/config/SinglePageAppConfig.java[resource handler] to redirect all non-asset requests to the index.
You can remove it if you choose to use memory history (no URL change) or hash history (/#/login, /#/private).
We use https://learnboost.github.io/stylus/[stylus] as a css preprocessor. We also leverage two stylus modules:
- https://github.com/tj/nib[nib], which provides interesting mixins
- http://jeet.gs/[jeet], a powerful grid system
See examples of jeet http://codepen.io/collection/eilAH/[here].
In development, the styles are included by webpack, which enables hot reloading. In production, we use the https://github.com/webpack/extract-text-webpack-plugin[Extract Text Plugin] to extract the css to a separate file.
If you want to include static assets like images in the project, please see https://github.com/geowarin/boot-react/issues/16[this issue], which explains how to use the URL loader.
I’m real bad at creating logos but if you have time, I would be happy to include this by default in the project.
Running the tests
The check tasks will run the tests in both the frontend and the backend:
You can run the backend/frontend tests only with:
To test the backend, we use a simple https://github.com/geowarin/spring-spock-mvc[library] that wraps spring mvc tests and makes them a bit nicer to read. See the https://github.com/geowarin/boot-react/blob/master/backend/src/test/groovy/react/auth/AuthenticationSpec.groovy[auth-spec] for an example.
To test the frontend, we use https://github.com/airbnb/enzyme[enzyme].
This command will generate an optimized bundle and include it in the jar.
./gradlew clean assemble
You can then launch it with:
java -jar build/libs/boot-react-0.0.1-SNAPSHOT.jar
With spring boot 1.3, you can install the application http://docs.spring.io/spring-boot/docs/current-SNAPSHOT/reference/html/deployment-install.html#deployment-service[as a linux service]
NB: each application can be assembled with the
assemble task so you can use
The backend task depends on the frontend task.
The project can create a docker container.
And it will create a docker image named
> docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE boot-react/boot-react latest 5280d39f660f About a minute ago 138.9 MB
You can then run it with:
docker run -p 8080:8080 boot-react/boot-react
You can also pass arguments to the application like this:
docker run -p 8080:8080 boot-react/boot-react --spring.profiles.active=redis --spring.redis.host=redis
There is a simple
docker-compose.yml in the root directory of the project.
Once you have built the application image with
./gradlew backend:buildDocker, you can run:
docker-compose up -d
This will run the application together with a redis server.