andrew
/
RailSignalAPI
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
An app for tracking and managing your rail systems, in real time.
41 Commits 1 Branch 9 Tags 605 KiB
Java 43.4%
Vue 27%
JavaScript 19.3%
Lua 6.8%
D 2.2%
Other 1.3%
Go to file
Andrew Lalis 637dee747d Added working installer workflow 2022-05-29 22:12:24 +02:00
.mvn/wrapper Added all basic infrastructure. 2021-11-21 23:46:01 +01:00
quasar-app Added first implementation of CC:Tweaked driver and improved UI. 2022-05-29 17:02:05 +02:00
src Added working installer workflow 2022-05-29 22:12:24 +02:00
.gitignore Added build_system.d and changed to --mode=development. 2022-05-08 20:04:21 +02:00
LICENSE Initial commit 2021-11-21 13:44:20 +01:00
README.md Added first implementation of CC:Tweaked driver and improved UI. 2022-05-29 17:02:05 +02:00
build_system.d Added settings, updated build system for quasar. 2022-05-24 10:38:42 +02:00
component-drivers.md Added first implementation of CC:Tweaked driver and improved UI. 2022-05-29 17:02:05 +02:00
mvnw Added all basic infrastructure. 2021-11-21 23:46:01 +01:00
mvnw.cmd Added all basic infrastructure. 2021-11-21 23:46:01 +01:00
pom.xml Added stuff. 2022-05-12 22:10:42 +02:00

README.md

Rail Signal

A comprehensive solution to tracking and managing your rail system, in real time.

Development

To work on and develop Rail Signal, you will need to run both the Java/Spring-Boot backend API, and the Vue/Quasar frontend app.

To start up the API, the project directory in IntelliJ (or the IDE of your choice), and run the RailSignalApiApplication main method.

To start up the app, open a terminal in the quasar-app directory, and run quasar dev.

Building

To build a complete API/app distributable JAR file, simply run the following:

./build_system.d

Note: The build script requires the D language toolchain to be installed on your system. Also, you can compile build_system.d to a native executable to run the build script more efficiently.

This will produce a rail-signal-api-XXX.jar file in the target directory, which contains both the API, and the frontend app, packaged together so that the entire JAR can simply be run via java -jar.