Skip to content

Latest commit

 

History

History
68 lines (45 loc) · 1.85 KB

dev.md

File metadata and controls

68 lines (45 loc) · 1.85 KB
Raw

Developing ampd

Building from source

Dependencies:

If you like to make some small changes to ampd or just build your own application from source, clone (or fork) this repository:

git clone https://github.com/rain0r/ampd

To get a fully runing ampd you can just use type:

mvn package

This will:

  • Build the Angular frontend and place the files under src/main/resources/static
  • Build the whole Spring Boot application and packge it into a runnable jar-file

Working on the frontend

Getting the frontend up and running is as easy as:

cd angularclient/
npm install
ng serve

On OSX, the package needs to be installed as well:

npm i --no-save fsevents

The flag --no-save prevents it from showing up under dependencies (since it's only needed on OSX).

This should get you started, you can see the UI at http://localhost:4200/ but ampd won't connect to the backend server. If you already have a running ampd instance, you can tell the frontend to use that: Open the file angularclient/src/environments/environment.ts and set change AMPD_URL in the first line to your computer name or ip. Run ng serve again and - provided there is a ampd instance running on that address - the frontend will connect to that.

Working on the backend

To get it all up and running, just hit mvn spring-boot:run. By default, this would also build the Angular frontend. If you want to skip that, pass the -Dskip.npm=true flag to Maven: mvn -Dskip.npm=true spring-boot:run

# Building ampd for use under the context /my-music/

mvn  -Dfrontend.context=/my-music/ compile

After that, you can start the resulting jar file:

java -jar target/ampd-*.jar