Repository navigation
feat: add spring boot and react starter - #1
Merged
Merged
Conversation
- /api/v1 health and messages endpoints with matching schemas - native SQL queries on JpaRepository, actuator removed - Flyway migrate and status tasks running in containers - spec exported to backend/openapi.json with a no-database profile - frontend matches the typescript starter, dev uses dev:up and dev:down - same mise tasks and CI jobs as the other starters
- add a short docs/ARCHITECTURE.md with the request flow
- health no longer queries the database - rename stack:dev:* to docker:dev:* - fold db:dev:down into db:dev:stop, which keeps the data - make func-style a lint warning
- force colors for tasks and the dev web container - rename db:dev:start and db:dev:stop to db:dev:up and db:dev:down
- use @requiredargsconstructor instead of hand-written constructors - document the pattern in the backend rules
- add RequestLogger, a servlet filter matching the other starters' format - skip successful health checks, warn on 4xx, error on 5xx
- apply and check migrations with the Flyway CLI from mise, using DATABASE_URL from .env - stop the dev backend from migrating on start; deploys still do - setup installs deps, migrates and generates the contract, like the other starters - drop the Flyway Gradle plugin - shorten console logs to date, level, logger and message - stop serving the OpenAPI spec at runtime - remove PORT and LOG_LEVEL defaults from application.yaml
- pass DATABASE_URL to Flyway in the migrate tasks instead of templating it in [env]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
com.example.app, withcontroller -> service -> dao -> repository -> entitylayers and one route,GET /api/messagesV1__create_messages.sqlcreates themessagestable and inserts a row. Hibernate only validates the schemamise run db:dev:migration <name>diffs the entities against the dev db and writes the next migration with Hibernate's update scriptcontract/openapi.json(committed), and hey-api generates the frontend client from it/apireverse proxy and SPA fallback from the Khoury boilerplate, no caching or authcompose.yamlruns the deploy images,compose.override.yamlruns dev targets with bind mounts..envreaches the app only through compose, so runningbootRunorviteon the host fails on purposeAGENTS.mdand.agents/rules/hold a few basic code rules for students to build on