Skip to main content

Autoreloading your UI pages in the browser with each build, while developing web apps in Spring boot



I had been working on a simple gradle project where I use Spring boot to develop the backend and REST API using Spring data REST and Frontend using Vue.js + spring boot thymeleaf. Spring boot's controllers will handle the routing and all frontend work can be done in the html pages.

I will post these other pieces separately.

If you have done this, you may know that you can load your .html pages using Spring Boot's Thymeleaf rendering engine which comes configured by default. As long as you place them under src/main/resources/templates (default location for renderable templates)

But once that page is rendered you can use any frontend framework on it. In my case, I am using Vue.js as the frontend framework (more on this in other posts)

So if you have a spring boot project setup, you can install the spring boot devtools to your project. Once you do that, by default it will reload your spring boot application whenever your source code changes.

However, normally your html pages are going to be under src/main/resources/templates and these won't be automatically reloaded in the browser even if you refresh it. The reason is that those pages need to be built under build/ directory only then they will be re-served.

You can come up with a simple recipe such that when you save those pages, spring will reload your page in the browser!

Here is how

1. Setup spring-boot-devtools in your project by adding something like this to your dependencies

    runtime("org.springframework.boot:spring-boot-devtools")

2. Now add this to src/main/resources/application.properties

spring.devtools.restart.additional-paths=src/main/resources/templates,src/main/resources/static
 
Just add as many paths as you like to be watched by the autorestarter

That's it now you will need to leave your application running and build your project after changing the static files (you would not need to even build if you changed java files of course)

At this time, you still have to refresh your browser to reload the changes.

To make this even cooler, install (in chrome) the LiveReload extension

Now it will automatically reload your page just leave the browser open, every time you hit 'build' or run 'gradlew build'!

This is now almost as good (but not quite) as using grunt watch in NodeJS projects.


Labels:

Comments

Post a Comment

Popular posts from this blog

Sending Form data to a backend REST API using Axios

This need is incredibly common and useful, and hopefully will save you a lot of time when doing server side calls from your UI application (or even non UI clients like NodeJS applications) Example here is to send a POST request to an endoint /api/item/new (which will create a new item in the database). We will just assume tbhe backend is already setup (it's not relevant to this article). All we need to know is that we can do a POST /api/item/new and send it form data with two pieces of info     name, filter So, if you have a node.js application (I was using Vue-cli generated project, but it does not matter), install 'axios' (a most popular tool to make server calls these days) npm i axios --save OR yarn add axios (my preferred method) Now, in your service JS file (which is generally when I keep all my api calls) do something like this createNew ( name , filter ) { let formData = new FormData (); formData . append ( "name" , ...
Post a Comment
Read more

Unit testing code that uses environment variables and system properties with fakes

I did not exactly learn this today, but I am sharing it as I have found it extremely useful when unit testing code that depends on environment or system property settings. While I am using Java as an example, the general concepts apply any where. Problem : You have a piece of code you are unit testing that uses settings from env variables or system properties passed to the VM (System.getProperty), but you don't want the tests to be affected by the 'real' environment or system properties in the VM. So, your unit tests should not get different results or fail when the real environment changes. Solution : There are several. But the most straightforward is to use a mocking library to mock out the environment or fake it out, whatever your prefer. You can create a fake using a library like EasyMock, PowerMock etc. This I won't discuss in this post, since there are numerous articles for that. Or you can write a simple class that acts as a proxy, using the proxy pattern...
Post a Comment
Read more

CSS: em vs rem font sizes

 When do you use em and when do you use rem? If you have ever asked this, you are like me :) So welcome. Basically, to save you time here it is: - If you want your font-size relative to the container's font-size, use em - If you want your font-size relative to the 'root' (or html) element's font-size, use rem! If you just stop reading now that might be sufficient, but if you are more curious, go on. Example companion codepen: https://codepen.io/binodpanta/pen/RwLWRra Basically your page should ideally always have a default font-size specified for the root, such as  :root { font-size: 1em; } This typically becomes 16px default for the base font size. Now, if you use rems in your elements' styles you get a consistent scaling wrt this number! so if you do div.someclass { font-size: 0.5rem; } you are going to always get a nice scaled font size regardless of screen size. So all your fonts will scale relatively throughout the app!  If you had used 0.5em, your calculated ...
Post a Comment
Read more