CreepyAgb

This project was generated with Angular CLI version 6.0.8.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

Deploy

Deployment via angular-cli-ghpages, follow the README for instructions.

There is no automated build or deployment setup.

Edit: Due to a wrong link being sent around, we need to account for people trying to access the app via the /select and /services routes directly. I hacked around that with static html files that just redirect to / where the app should load. While this works, it makes the deploy process a bit more of a hassle. The template file is in src/services.html, I copied it over manually to dist/creepy-agb/services.html, dist/creepy-agb/select.html, dist/creepy-agb/services/index.html, dist/creepy-agb/services/index.html. That should cover all the cases.

So the steps would be:

• $ ng build --prod --base-href "https://datenschule.github.io/creepy-agb/"

• copy over all static html

• $ angular-cli-ghpages

• This creates an creepy-agb folder on gh-pages. Pull from that branch. Move the contents to root with $ mv creepy-agb/* . and commit and push.

Data

The data used in the project was manually collected as part of Data Expedition