Deployment preparation workspace

Prepare your SalesSavvy backend for cloud deployment.

This browser app cannot directly clone GitHub repositories, provision MySQL, or publish a live server from the sandbox. It gives you a production-ready deployment plan, environment configuration, build scripts, and verification checklist for your Spring Boot repository.

Java 17

Preferred runtime

MySQL

Cloud env variables

JAR

java -jar launch

Repository target

Generate commands from your GitHub URL.

Ready
Enter the repository URL and generate a deployment kit. No deployment has been performed yet.

Cloud checklist

1

Clone repository

git clone the GitHub project into the deployment workspace.

2

Detect build tool

Use pom.xml for Maven or build.gradle/settings.gradle for Gradle.

3

Use Java 17

Configure JAVA_VERSION=17 or a Java 17 runtime image.

4

Patch configuration

Replace local Workbench credentials with DB_* environment variables.

5

Build runnable JAR

Run Maven or Gradle package while skipping tests only if CI requires it.

6

Detect main class

Spring Boot plugin normally writes the executable manifest.

7

Run service

Start with java -jar target/*.jar or build/libs/*.jar.

8

Health check

Verify /actuator/health or a real controller endpoint.

9

Auto redeploy

Connect the host to GitHub push events for the main branch.

Generated deployment logs

Preparation output only; run these commands in your CI/CD or host shell.

$ Waiting for deployment kit generation...

application.properties patch

Use this cloud-safe configuration for MySQL and dynamic server port.

server.port=${PORT:8080}

# Cloud MySQL configuration
spring.datasource.url=jdbc:mysql://${DB_HOST}:${DB_PORT:3306}/${DB_NAME}?useSSL=true&requireSSL=false&allowPublicKeyRetrieval=true&serverTimezone=UTC
spring.datasource.username=${DB_USERNAME}
spring.datasource.password=${DB_PASSWORD}
spring.datasource.driver-class-name=com.mysql.cj.jdbc.Driver

# Hibernate / JPA production defaults
spring.jpa.hibernate.ddl-auto=update
spring.jpa.show-sql=false
spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQLDialect
spring.jpa.properties.hibernate.format_sql=false

# Actuator health checks
management.endpoints.web.exposure.include=health,info
management.endpoint.health.probes.enabled=true
management.health.db.enabled=true

# Safer error output
server.error.include-message=never
server.error.include-stacktrace=never

Required environment variables

Set these in Render, Railway, Fly.io, Heroku-compatible platforms, or your container host.

✓

DB_HOST

Cloud MySQL hostname

✓

DB_PORT

MySQL port, usually 3306

✓

DB_NAME

Production database name

✓

DB_USERNAME

Database user with app permissions

✓

DB_PASSWORD

Database password stored as a secret

✓

PORT

Provided by the hosting platform; defaults to 8080

Verification commands

Replace the domain with your actual public backend URL after deployment. A live URL cannot be produced from this static sandbox.

# After deployment, set BACKEND_URL to your public service URL
export BACKEND_URL=https://your-deployed-backend-host

# Health check if Spring Boot Actuator is enabled
curl -i "$BACKEND_URL/actuator/health"

# Discover exposed routes from logs or controller mappings
# Then test one real REST endpoint, for example:
curl -i "$BACKEND_URL/api/products"

# Confirm CORS preflight behavior
curl -i -X OPTIONS "$BACKEND_URL/api/products" \
  -H "Origin: https://your-frontend-domain" \
  -H "Access-Control-Request-Method: GET"
Copied to clipboard
⚡Built with GenMB
Built with GenMB