https://github.com/agregory999/angular4pcf
https://github.com/agregory999/angular4pcf
angular4 pcf
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/agregory999/angular4pcf
- Owner: agregory999
- Created: 2017-10-31T15:31:45.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-11-01T17:45:19.000Z (over 8 years ago)
- Last Synced: 2025-02-16T21:46:23.601Z (over 1 year ago)
- Topics: angular4, pcf
- Language: TypeScript
- Size: 80.1 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Property
This project was generated with [Angular CLI](https://github.com/angular/angular-cli) version 1.4.9.
## Development server
DO NOT RUN the development server, as the config properties must be generated by a PCF buildpack
## 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`.
## Secret Sauce
1) .profile - this tells the static buildpack to run the enclosed script, which grabs environment settings and inserts them into a file called config.json in the document root of the Angular app.
2) package.json - look for the post-build script that copies the .profile into the resulting dist/ directory we deploy to PCF.
3) Service - this one is called "dynamic" - look in src/app/properties - This service queries the `/config.json` file that is generated at deploy time.
4) manifest.yml (for PCF) - In here we set the buildpack, lower the memory in use, and set some sample environment properties that will be retreived using the `.profile` script.
## Build
Upon first download of this repo, run `npm install` to bring in the required packaged and create the `node_modules` directory.
Run `npm run build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `-prod` flag for a production build.
To deploy, run `cf push`. The reason this works with teh static buildpack is due to the presence of the manifest file with the static buildpack.
## Property Changes
To change a config property, use cf set-env and then restage the application.
Using `cf ssh ` you can then view the new config.json within `app/public` inside the container.
## Running unit tests
Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
## Running end-to-end tests
Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
## Further help
To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
=======
# Angular4PCF