Deploy SpringBoot Apps Instantly with IDEA + Docker: One-Click Remote Setup

You shouldn't still be manually building jar files, uploading them, and running java -jar to deploy projects; this guide teaches you to use IDEA + Docker for one‑click remote deployment.

1. Introduction

This article teaches how to use IDEA + Docker to remotely deploy a SpringBoot project, comparing it with the traditional method of uploading a jar to a server and running it, dramatically improving deployment efficiency.

2. Jar Package Deployment vs Remote Deployment

Jar Package Deployment

Normally you install Java on the server, upload the locally built jar, and start it with java -jar. Each redeployment requires stopping the app, uploading a new jar, and restarting, which is cumbersome and makes log viewing difficult.

IDEA + Docker Remote One‑Click Deployment

After configuring the environment, redeploying only requires clicking a green triangle to complete the deployment automatically.

You can also conveniently view real‑time logs.

3. Configure Remote Deployment

(1) SSH Configuration

To connect to the server you must configure SSH (File → Settings → Search "ssh"). It is recommended to use the "Key pair" authentication type, though you can start with "Password" and switch later if needed.

(2) Connect Docker Daemon

Next configure the connection to the Docker daemon (File → Settings → Search "docker").

(3) Write Dockerfile

Create a Dockerfile to define the image for your SpringBoot application. Adjust the file according to your project needs.

# Base image
FROM openjdk:17
# Copy jar to image (place the jar in the same directory as the Dockerfile)
ADD target/demo-0.0.1-SNAPSHOT.jar app.jar
# Container start command
ENTRYPOINT ["java","-jar","/app.jar","--spring.profiles.active=prod"]
# Expose port
EXPOSE 8080

(4) Set Up Remote Deployment

1) Create a new deployment configuration.

2) Fill in the previously configured SSH and Docker settings.

3) Click the green triangle to deploy automatically.

After deployment the application starts, logs appear, and the browser shows the expected response.

Now the tutorial ends. The initial setup may be a bit involved, but subsequent deployments become extremely convenient.