Ordinary project background packaging process

Common project background packaging (jar) process

  1. I believe that none of my bloggers are experienced programmers! Basically, they are all developed in local databases! First of all, they must change their local libraries to remote databases.
  2. Start packaging (maybe you will see some people package not the install but the package, this does not affect, install will have an additional compilation process, you can determine according to your needs)Insert picture description here
  3. After the packaging is complete, a file will appear in your project directory. I have removed this jar and you can see the jar file.
  4. Insert picture description here
  5. Generally speaking, the name of the jar file you packaged cannot be matched with your front end. Putting it directly on the server will directly cause the 404 problem, so you should go to the remote location of your project to check the name of your original project packaging. , Change to the original name! Of course there is a second method to determine what you want to change the name, is to view the address of the remote reverse proxy configured by the front-end config.js, and the port number is your back-end Package project name!
  6. Before replacing your jar package, it is best to turn off tomcat first, and then upload the jar package.I close tomcat here and directly close the corresponding cmd window.If the corresponding cmd window cannot be found, switch the user to turn off, and then switch back The original user, upload the jar package, click start.bat after uploading, it
    is very simple and convenient to share with everyone, I hope it is useful to everyone
Published 34 original articles · won praise 0 · Views 3634

Guess you like

Origin blog.csdn.net/qq_43469899/article/details/103309349