Reformatted code
This commit is contained in:
+8
-1
@@ -3,16 +3,21 @@
|
||||
This application exists as an example for the Lightrun series of articles.
|
||||
|
||||
## Building
|
||||
|
||||
This application requires [Apache Maven](https://maven.apache.org/) and [Java 17+](https://www.oracle.com/java/technologies/downloads/).
|
||||
|
||||
Building the code is done by executing:
|
||||
|
||||
```
|
||||
$ mvn install
|
||||
```
|
||||
|
||||
from the top level.
|
||||
|
||||
## Running
|
||||
|
||||
The application consists of three services:
|
||||
|
||||
* Tasks
|
||||
* Users
|
||||
* API
|
||||
@@ -23,7 +28,9 @@ The Tasks and Users services exist as microservices for managing one facet of da
|
||||
|
||||
This does mean that the startup order is important. The JMS queue exists within the Tasks service and is connected to from the Users service. As such, the Tasks service must be started before the others.
|
||||
|
||||
Each service can be started either by executing `mvn spring-boot:run` from within the appropriate directory. Alternatively, as Spring Boot applications, the build will produce an executable JAR file within the `target` directory that can be executed as, for example:
|
||||
Each service can be started either by executing `mvn spring-boot:run` from within the appropriate directory. Alternatively, as Spring Boot applications, the build will produce an executable JAR file within the `target` directory that can be executed as, for
|
||||
example:
|
||||
|
||||
```
|
||||
$ java -jar ./target/tasks-service-0.0.1-SNAPSHOT.jar
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user