feat: jpa, messaging, notification, mongo, graphql 어댑터터 리펙토링
This commit is contained in:
@@ -0,0 +1,36 @@
|
||||
# =============================================================================
|
||||
# A local opt-in example: the five adapters are off in the shipped defaults, and this shows what
|
||||
# turning some of them on looks like. Copy to src/.env.local and edit.
|
||||
#
|
||||
# Each switch here needs the infrastructure its Compose profile provides. Turning one on without
|
||||
# it is refused at startup by CapabilityDependencyValidator, which names the missing value.
|
||||
# =============================================================================
|
||||
|
||||
SPRING_PROFILES_ACTIVE=local
|
||||
|
||||
# JPA: needs the PostgreSQL service. Flyway owns the schema from dev onward, and local uses the
|
||||
# same vendor semantics so the two do not diverge.
|
||||
APP_PERSISTENCE_JPA_ENABLED=true
|
||||
APP_DATASOURCE_URL=jdbc:postgresql://localhost:5432/ca_skeleton
|
||||
APP_DATASOURCE_USERNAME=ca_skeleton
|
||||
APP_DATASOURCE_PASSWORD=
|
||||
APP_DATASOURCE_DDL_AUTO=validate
|
||||
|
||||
# Messaging: the broker id selects the transport; the switch decides whether there is one at all.
|
||||
APP_MESSAGING_ENABLED=false
|
||||
APP_MESSAGING_BROKER=
|
||||
|
||||
# Outbox: needs JPA and messaging together, and a broker. relay-enabled only starts the scheduler.
|
||||
APP_OUTBOX_ENABLED=false
|
||||
APP_OUTBOX_RELAY_ENABLED=false
|
||||
|
||||
# Mongo: active-profile is required when the switch is on, and selects exactly one client.
|
||||
APP_PERSISTENCE_MONGO_ENABLED=false
|
||||
APP_PERSISTENCE_MONGO_ACTIVE_PROFILE=
|
||||
|
||||
# GraphQL: the deployment mode must match the runtime environment (local -> LOCAL).
|
||||
APP_GRAPHQL_ENABLED=false
|
||||
APP_GRAPHQL_DEPLOYMENT_MODE=LOCAL
|
||||
|
||||
# Notification: stores requests relationally, so it needs JPA on.
|
||||
APP_NOTIFICATION_PLATFORM_ENABLED=false
|
||||
Reference in New Issue
Block a user