![]() 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. The option where I would need to set an environment variable LRPortOverride containing the new port number seemed feasible to me. ![]() Older versions of Python LiveReload used a Guardfile to describe optional additional rules for files to watch and build commands to run on changes. By default, it will listen to port 35729, the common port for LiveReload browser extensions. So I started looking for a way to change the LiveReload server port for one of my two applications. Python LiveReload provides a command line utility, livereload, for starting a server in a directory. 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. 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!). Simply add the following to your application.yml (or properties equivalent). Of course disabling the live-reload completely will work, but there's also a property you can set to choose a different port. Please make sure that LiveReload 2. ![]() In my case I have two Spring Boot services running simultaneously too. The Chrome LiveReload plugin reports 'Could not connect to LiveReload server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |