Deploy

Goal

This snapshot advances Ironclad Gazette by teaching you to prepare Ironclad Gazette for Railway and managed MySQL.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Java 17+, Maven, a terminal, and Docker for MySQL stages. You should recognize classes, annotations, and HTTP verbs.

Port 8080 must be free. Copy .env.example before starting database stages.

• Java 17 and Maven
• A code editor and terminal
• Docker from part 4 onward

Concepts

Production needs HTTPS, environment-only database credentials, and no secrets in the repository.

Keep controllers thin: accept input, delegate to repositories or services, and let Thymeleaf escape output by default.

Walkthrough

Review DEPLOY.md, set DATABASE_URL and DB credentials on Railway, and never commit .env.

Read the example, then open the matching snapshot. The repository includes the surrounding setup and error handling.

spring.datasource.url=${DATABASE_URL}
# Set on Railway only

Run and verify

Enter 12-Deploy, start MySQL when needed, copy .env.example, and run mvn spring-boot:run on port 8080.

Open http://127.0.0.1:8080. Watch the terminal for validation and database errors.

docker compose -f ../docker-compose.yml up -d
git clone https://github.com/michaeldunga1/fcc-spring-blog.git
cd fcc-spring-blog/12-Deploy
cp .env.example .env
mvn spring-boot:run

Troubleshooting

If the app cannot reach MySQL after deploy, confirm JDBC URL and firewall rules on the host.

Connection refused usually means Docker MySQL is stopped or the port is not 3308. For auth issues, confirm you are using email (not username) on the login form.

• Read the first error first
• Restart after environment changes
• Never commit .env or uploads

Try this

List every secret that must live only in the Railway environment.

Test a happy path and one invalid or unauthorized request.

• Make one small change
• Test it in the browser
• Compare with the next snapshot only after it works