Skip to content

GuardianTheater/guardian-theater

 
 

Repository files navigation

Guardian Theater

This fork is now host to d1.guardian.theater, the Destiny 1 version of Guardian Theater. It will hopefully change very little from here on out.

For active development of guardian.theater, see: https://github.com/chrisfried/guardian-theater-ng2

This project was generated with angular-cli version 1.0.0-beta.24.

Getting up and running

You'll need:

For the development server to run you must have a certificate it can load. Do so by issuing the following command:

openssl req -new -x509 -newkey rsa:2048 -sha256 -nodes -keyout dev.key -days 3560 -out dev.crt -config docker/ssl/certificate.cnf

You must also create a src/environments/keys.ts file with your key in it. The file looks like this:

export const bungieDev = {
  apiKey: '$BUNGIE_DEV_API_KEY',
  authUrl: 'https://www.bungie.net/en/OAuth/Authorize',
  clientId: '$BUNGIE_DEV_CLIENT_ID',
  clientSecret: '$BUNGIE_DEV_CLIENT_SECRET'
}
export const bungieProd = {
  apiKey: '$BUNGIE_PROD_API_KEY',
  authUrl: 'https://www.bungie.net/en/OAuth/Authorize',
  clientId: '$BUNGIE_PROD_CLIENT_ID',
  clientSecret: '$BUNGIE_PROD_CLIENT_SECRET'
}

Replace the variables with your own values and save the file.

Last, run npm install to install all requirements.

Development server

Run npm start for a dev server. Create a hosts entry for dev.guardian.theater pointing to your localhost. Navigate to http://dev.guardian.theater:3000/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run npm run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.

Build

Run npm 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 npm run ng test to execute the unit tests via Karma.

There are no tests, just boilerplate generated by Angular CLI. If you would like to write tests, you are more than welcome to.

Running end-to-end tests

Run npm run ng e2e to execute the end-to-end tests via Protractor. Before running the tests make sure you are serving the app via ng serve.

There are no tests, just boilerplate generated by Angular CLI. If you would like to write tests, you are more than welcome to.

Deploying to Github Pages

Run npm run ngh to deploy to Github Pages.

Further help

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

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 91.7%
  • HTML 4.4%
  • CSS 3.7%
  • JavaScript 0.2%