You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,29 +30,36 @@ Starting the server is relatively easy. There are two ways of doing this:
30
30
31
31
To run the application through SBT, run the following command:
32
32
33
-
>sbt container:start shell
33
+
sbt container:start shell
34
34
35
35
It might take some time to compile if you haven't done this yet and then you will see a shell. Then your service will become available and you will be able to query it through the browser.
36
36
37
37
To stop the server, run:
38
38
39
-
>container:stop
39
+
container:stop
40
40
41
41
### Running the Server Through a Fat JAR
42
42
43
43
For this operation you will need to create the fat jar first and then simply start it as normal Java application.
44
44
45
45
To build the fat jar:
46
46
47
-
>sbt assembly
47
+
sbt assembly
48
48
49
49
To run the application:
50
50
51
-
>java -jar jar-name.jar
51
+
java -jar jar-name.jar
52
52
53
53
Then to stop the application, just press Ctrl+C.
54
54
55
+
Skeleton
56
+
--------
57
+
58
+
We have a basic skeleton with almost no functionality that can be used to quickly start developing new APIs.
59
+
60
+
It is on the following branch: [feature/Scala_Api_Skeleton](https://github.com/nikolovivan/scala-api/tree/feature/Scala_Api_Skeleton). Just clone it and you are ready to go!
61
+
55
62
Conclusion
56
63
----------
57
64
58
-
This is the skeleton application you can use to quickly start your development. From then on, it is up to you to add the dependencies you need and make the API do whatever you want.
0 commit comments