To the Spring application.properties of one of my applications, and the issue was fixed. This confirms my conclusion and also provides a solution for my problem. Thus, my search continued and I finally found this: However, no matter what I tried, my environment variable was simply ignored. With ATOM you do not click the link in the bottom of the screen you have to manually start it using: Packages > LiveReload > Toggle Server. The option where I would need to set an environment variable LRPortOverride containing the new port number seemed feasible to me. (We recommend guard-livereload, until LiveReload 2 comes to your platform. So I started looking for a way to change the LiveReload server port for one of my two applications. Please make sure that a compatible LiveReload server is running. The LiveReload server is then also started twice, while the port it wants to use (35729) can obviously be bound to only once. In my case I'm running 2 Spring Boot applications simultaneously, which is exactly the reason for this warning. npm install connect-livereload -save-dev use. Like you said, it's not preventing your app from working properly, it's just that I'd like to avoid warnings wherever possible (especially the ones I can not explain!). connect middleware for adding the livereload script to the response. Simply add the following to your application.yml (or properties equivalent). Hi I’ve got a serious problem about my livereload since I upgraded Ionic CLI to the latest version (3.5) with the latest Cordova CLI (7.0). ![]() Of course disabling the live-reload completely will work, but there's also a property you can set to choose a different port. ![]() In my case I have two Spring Boot services running simultaneously too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |