This project was generated with Angular CLI version 1.6.1.
This project contains a prototype for a VMware VM console app utilizing Angular and WebMKS.
Settings are currently configured in src/environments/. Please update the URLs in those files to set the appropriate host:port for the player.vm.api.
Run ng serve for a dev server. Navigate to http://localhost:4305/. The app will automatically reload if you change any of the source files.
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.
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.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.
All configurable values - URLs, etc. - should be made to use the SettingsService. The SettingsService loads its values from configuration files located in /assets/config/. There are two files used for this. They are as follows:
- settings.json: This file is committed to source control, and holds default values for all settings. Changes should only be made to this file to add new settings, or change the default value of a setting that will affect everyone who pulls down the project.
- settings.env.json: This file is not committed to source control, and will differ for each environment. Settings can be placed into this file and they will override settings found in
settings.json. Any settings not found in this file will default to the values insettings.json.
In a production environment, settings.env.json should contain only the settings that need to be changed for that environment, and settings.json serves as a reference for the default values as well as any unchanged settings. settings.json should not be altered in a production environment for any reason.
Think you found a bug? Please report all Crucible bugs - including bugs for the individual Crucible apps - in the cmu-sei/crucible issue tracker.
Include as much detail as possible including steps to reproduce, specific app involved, and any error messages you may have received.
Have a good idea for a new feature? Submit all new feature requests through the cmu-sei/crucible issue tracker.
Include the reasons why you're requesting the new feature and how it might benefit other Crucible users.
Copyright 2021 Carnegie Mellon University. See the LICENSE.md files for details.