This is the backend (for frontend) for dancier.
We are working locally with a docker-compose setup, that launches every needed service.
Before you run it the first time, you have to set this up....
You have to have maven, docker and docker-compose being installed.
Then in the project root folder create the following directories with the proper rights.
# for the pg-admin volume
mkdir -p volumes/pg-admin-data
# for the kafka volume
mkdir -p volumes/kafkaYou can now access the database GUI with your browser:
| User | Pass |
|---|---|
| [email protected] | secret |
Here you can configure the connection to the postgres instance:
| Hostname | database | user | pass |
|---|---|---|---|
| dancer-db | dancer | dancer | dancer |
(assuming the docker-compose setup is up and running)
./mvnw clean install -DskipTests; docker-compose up --build./mvnw clean install(assuming the docker-compose setup is up and running)
# stopping dancer in docker-compose
docker-compose stop dancer;
# running the boot app with overwriting the needed host
./mvnw spring-boot:run -Dspring-boot.run.arguments="--spring.datasource.url=jdbc:postgresql://localhost:5432/dancerShow test coverage in target/site/jacoco/index.html: `.target/site/jacoco/index.html
When working locally the mailing-system of the backend is configured to not send the mails, but to dump them only to the log. This is achieved by using spring profiles. The profile here is 'dev'. So make sure to not change the profile unintentionally.
As long as we are not live, this is the only other environment next to working locally. The corresponding Profile is 'staging'
Mail will be send via an SMTP-Server. But the target addresses of all mails are rewritten to always go to a configurable mail-address.