when u connecting domain domae to it ,how you make it work like ,if there is nginx webs erver you can reverse proxy it by giving the port ,her ehow you do it
I have one last question, how do we get the jar to always be published and not crash? is that every time I close the terminal I can no longer even register and obtain data from the API, as we do so that that java-jar file.jar service does not crash and remains.
@@Rohityadav-tj2bz thanks, I needed this. But one question, if I'd want to do not let the job running in the background anymore, how could I handle this? Is there any command which I can use it?
@@pedrovictorsaraiva8705 just do the jobs command it will show up the list of jobs running in the background just get the process Id of the jobs and do kill command it will kill
Chala manchi informational video... Thank you Hameed
Thanks you for nice illustration !!
nice explanation..and very clear
Great explanation! Your battery percentage was giving me anxiety though.
Thanks a lot. It helped me
Thanks, very usefull video!
Thank you sir
when u connecting domain domae to it ,how you make it work like ,if there is nginx webs erver you can reverse proxy it by giving the port ,her ehow you do it
can't connect to the ec2 public dns
I have one last question, how do we get the jar to always be published and not crash? is that every time I close the terminal I can no longer even register and obtain data from the API, as we do so that that java-jar file.jar service does not crash and remains.
Run jar with nohup command and & it will start job in the background and will work even if you logged out of AWS ec2
@@Rohityadav-tj2bz thanks, I needed this. But one question, if I'd want to do not let the job running in the background anymore, how could I handle this? Is there any command which I can use it?
@@pedrovictorsaraiva8705 just do the jobs command it will show up the list of jobs running in the background just get the process Id of the jobs and do kill command it will kill