1. Переключиться на ветку dev [скорее всего опционально]
2. Создать токен для чтения пакетов (тыкнуть сюда и поставить галочку только на read:packages)
3. Добавить локально две переменные окружения GITHUB_USERNAME, GITHUB_TOKEN (на маке я просто писал в терминале echo GITHUB_USERNAME="kalkolay" и аналогично токен)
4. mvn install -U -s settings.xml
5. mvn clean install
6. В IDE нажать Edit configurations -> Active profiles и написать dev

Если по-прежнему не сработало, можно попробовать переоткрыть проект и попробовать заново 4 и 5 шаги.

1. cd в корень директории демосервиса и git clone https://github.com/andrsuh/tiny-event-sourcing.git
2. Билдим склонированный проект: cd tiny-event-sourcing и правой кнопкой на pom.xml -> жмём на предпоследнюю опцию Add to Maven или что-то такое, делаем mvn install и билдим проект
3. Возвращаемся в корневую папку нашего проекта, добавляем файл tiny-event-sourcing-lib/target/tiny-event-sourcing-lib-2.0.1-SNAPSHOT.jar командой: mvn install:install-file -Dfile=<path-to-file> -DpomFile=<path-to-pomfile>
4. Делаем как для запуска проекта mvn install -U -s settings.xml && mvn clean install
5. Билдим наш проект, для теста можно написать import ru.quipy.* (где-нибудь в сорцах, но не в мэйне) и посмотреть подсветит ли идея эту строку красным

• Create template repository with the name GROUP-ID-YOUR-APP-NAME and select this organization as an account

• Rename name, description, github to corresponding values in pom.xml

• Rename postgres-app to postgres-YOUR-APP-NAME, image to ghcr.io/USERNAME/REPOSITORY in docker-compose.yml

• Configure settings.xml *

  • First option: settings in local maven repository (~/.m2/settings.xml)
  • Second option: settings in project root
  • Settings can be specified using:
    • mvn -s settings.xml
    • IDEA: Maven settings -> User settings file
  • Settings must contain dummy mirror to override default blocking mirror that blocks http

  <mirrors>
    <mirror>
      <id>maven-default-http-blocker</id>
      <mirrorOf>dummy</mirrorOf>
      <name>Dummy mirror</name>
      <url>http://0.0.0.0/</url>
    </mirror>
  </mirrors>
  

• For local app launch, use dev profile. It uses in-memory database

• For production deploy, run app with no profile

• Your app docker image will be automatically built and available at ghcr.io/username/repository

• You can override app version using environment variable APP_VERSION, e.g. APP_VERSION=0.1.0-SNAPSHOT docker compose up -d

• To run project on shared instance do cp docker-compose.override.example.yml docker-compose.override.yml. It will join the infra network with Logstash, etc

• POST /authentication: Authenticate
• POST /authentication/refresh: Refresh authentication

• POST /users: Register
• POST /authentication: Authenticate
• POST /authentication/refresh: Refresh authentication
• GET /users/me: Get information about current user
• DELETE /users/me: Delete current user

• POST /tasks: Create task
• GET /tasks: Get all tasks
• GET /tasks/{id}: Get task
• POST /tasks/{id}/assignee/{username}: Assign task
• DELETE /tasks/{id}: Delete task

• GET /swagger-ui.html: Swagger UI
  • Paste bearer token to Authorize window to have access to secured endpoints

AuthService.authenticate -> UserService.getUser(username)

Authenticate

Request:

POST /authentication

{
    "username": "<username>",
    "password": "<password>"
}

Response:

{
    "accessToken": "<token>",
    "refreshToken": "<token>"
}

Access token should be used in all other requests as header: Authorization: Bearer <access token>

Refresh authentication

Request:

POST /authentication/refresh

As an auth token refresh token should be used in request header: Authorization: Bearer <refresh token>

Output events:

• USER_CREATED
• USER_DELETED

Input events:

• USER_DELETED - Remove all tasks created by deleted user, remove assignee from tasks assigned to him

Output events:

• TASK_CREATED
• TASK_DELETED
• TASK_ASSIGNED

Input events:

• USER_CREATED - send greeting e-mail
• TASK_ASSIGNED - Notify user

@startuml
node UserModule
node TaskModule
node NotificationModule

'UserModule outputs
UserModule --> USER_CREATED
UserModule --> USER_DELETED

'TaskModule inputs
USER_DELETED --> TaskModule: Remove all tasks created by deleted user,\n \
remove assignee from tasks assigned to him
'TaskModule outputs
TaskModule --> TASK_CREATED
TaskModule --> TASK_DELETED
TaskModule --> TASK_ASSIGNED

'NotificationModule inputs
USER_CREATED --> NotificationModule: Send greeting e-mail
TASK_ASSIGNED --> NotificationModule: Notify user


@enduml

@startuml entities
entity User {
    username: text
    --
    * name: text
    * surname: text
    * email: string
}

entity Task {
    id: UUID (generated)
    --
    *author: User
    assignee: User
    *title: text
    description: text
    *status: Status
}

enum Status {
    TODO
    IN_PROCESS
    DONE
}

Task::author }o..|| User::username
Task::assignee }o..o| User::username
Task::status }o--|| Status
@enduml

Any module should be divided into api & impl base packages to define classes that can be used in other modules.

• users
  • api
    • controller
    • messaging
    • model
    • service
  • impl
    • entity
    • repository
    • service
• auth
  • api
    • controller
    • service
    • model
  • impl
    • config
    • service
• tasks
  • api
    • controller
    • messaging
    • service
  • impl
    • entity
    • repository
    • service
• notifications
  • api
    • controller
    • messaging
    • model
    • service
  • impl
    • config
    • entity
    • repository