Web implementation of the Gourmet Recipe Manager
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 

54 lines
1.4 KiB

#
# Application YML is used in production, filed under /BOOT-INF/classes.
# application.properties in the project root (working dir)
# is used in test.
#
# application config in execution current directory or ./config
# have higher precedence, and the command line is ultimate:
#
# https://docs.spring.io/spring-boot/docs/2.1.9.RELEASE/reference/html/boot-features-external-config.html
#
spring:
datasource:
#url: jdbc:sqlite:${home}/recipes.db
url: jdbc:mysql:dbase/recipes
# options: ${env} values
driverClassName: com.mysql.cj.jdbc.Driver
username: recipes
password: yumyumyum
jpa:
hibernate:
ddl-auto: none
database-platform: org.hibernate.dialect.MySQLDialect
# Tracking-modes prevent URL rewrite jsessionid on Primecases
# resources. Which causes "400" errors on initial main.jsf fetch.
server:
servlet:
session:
timeout: '30m'
tracking-modes: 'cookie'
# Theme here overrides joinfaces theme
# context-parameters:
# primefaces:
# THEME: vela
gourmet:
password:
file: .gourmetpw
joinfaces:
primefaces:
theme: bluesky
faces:
project-stage: Production
facelets-libraries: /tags/tags.taglib.xml
#logging:
# level:
# org.springframework.security: TRACE
# org.apache.catalina: TRACE
# jakarta.faces: TRACE
# com.sun.faces: TRACE
# jakarta.servlet: TRACE