In production, nabu can be probed with:
- http://localhost:9004/jersey/appstatus/up
- http://localhost:9004/jersey/appstatus/ready to check liveness and readiness, accordingly
server.port=9004
# activemq settings
spring.activemq.broker-url=tcp://activemq:61616
#spring.activemq.pooled=true
spring.activemq.user=admin
spring.activemq.password=admin
spring.jms.pub-sub-domain=true
# JPA settings (in-memory)
spring.jpa.show-sql=false
spring.jpa.hibernate.ddl-auto=create
# logging settings
logging.level.no.rutebanken=INFO
logging.level.org.apache=INFO
server.port=9006
# activemq settings
spring.activemq.broker-url=tcp://activemq:61616
#spring.activemq.pooled=true
spring.activemq.user=admin
spring.activemq.password=admin
# logging settings
logging.level.org.hibernate.tool.hbm2ddl=INFO
logging.level.org.hibernate.SQL=INFO
logging.level.org.hibernate.type=WARN
logging.level.org.springframework.orm.hibernate4.support=WARN
logging.level.no.rutebanken=INFO
logging.level.org.apache=WARN
# JPA settings (postgres)
spring.jpa.database=POSTGRESQL
spring.datasource.platform=postgres
spring.jpa.show-sql=false
spring.jpa.hibernate.ddl-auto=update
spring.database.driverClassName=org.postgresql.Driver
spring.datasource.url=jdbc:postgresql://nabudb:5432/nabu
spring.datasource.username=nabu
spring.datasource.password=topsecret
spring.datasource.username=postgres
spring.datasource.password=mysecretpassword
spring.datasource.initializationFailFast=false
-
Building
mvn clean install -
Building docker image (using profile h2 for in-memory DB)
mvn -Pf8-build,h2 -
Running
mvn spring-boot:run -Ph2 -Dspring.config.location=/path/to/application.properties -
Testing with curl
curl -vX POST -F "file=@\"avinor-netex_201609291122.zip\"" http://localhost:9004/jersey/files/21 -
Running in docker (development)
docker rm -f nabu ; docker run -it --name nabu -e JAVA_OPTIONS="-Xmx1280m -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005" --link activemq -p 5005:5005 -v /git/config/nabu/dev/application.properties:/app/config/application.properties:ro dr.rutebanken.org/rutebanken/nabu:0.0.1-SNAPSHOT -
Running in docker (test ++)
docker run -it --name nabu -e JAVA_OPTIONS="-Xmx1280m" --link activemq --link some-postgres -v /git/config/nabu/test/application.properties:/app/config/application.properties:ro dr.rutebanken.org/rutebanken/nabu:0.0.1-SNAPSHOT
To create the database for nabu, download and use the flyway command line tool: https://flywaydb.org/documentation/commandline/
Execute the migration. Point to the migration files in nabu.
./flyway -url=jdbc:postgresql://localhost:5433/nabu -locations=filesystem:/path/to/tiamat/src/main/resources/db/migrations migrate
./flyway -url=jdbc:postgresql://localhost:5433/nabu -locations=filesystem:/path/to/tiamat/src/main/resources/db/migrations migrate
Flyway 4.2.0 by Boxfuse
Database password:
Database: jdbc:postgresql://localhost:5433/nabu (PostgreSQL 9.6)
Successfully validated 1 migration (execution time 00:00.016s)
Creating Metadata table: "public"."schema_version"
Current version of schema "public": << Empty Schema >>
Migrating schema "public" to version 1 - Base version
Successfully applied 1 migration to schema "public" (execution time 00:04.220s).
To baseline an existing database that does not contain the table schema_version.
The schema of this database must be exactly equivalent to the first migration file. If not, you might be better off by starting from scratch and using the restoring_import to repopulate the new database.
./flyway -url=jdbc:postgresql://localhost:6432/nabu -locations=filesystem:/path/to/nabu/src/main/resources/db/migrations baseline
Create a new file according to the flyway documentation in the folder resources/db/migrations.
Commit the migration together with code changes that requires this schema change.