MaDgIK
/
monitor-dashboard
13
0
Fork 0
Code Issues Pull Requests Projects Releases 17 Wiki Activity
144 Commits 4 Branches 17 Tags 14 MiB
TypeScript 76.9%
HTML 19.1%
Less 2.3%
JavaScript 1.1%
CSS 0.6%
Go to file
Argiro Kokogiannaki 28e432bf54 [Monitor Dashboard|Trunk] 
Number indicators: 
	edit available only for portal admins
	parsing the url to parameterize and work for other indicators
	when requesting to get the numbers use the getNumberUrl to properly set the stakeholder id
	



git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-monitor-portal/trunk/monitor_dashboard@58924 d315682c-612b-4755-9ff5-7f18f6832af3
 		2020-06-16 07:30:45 +00:00
deploy [MOnitor Dashboard|Trunk] 2020-06-12 17:32:41 +00:00
src [Monitor Dashboard|Trunk] 2020-06-16 07:30:45 +00:00
README.md [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
angular.json [Monitor Dashboard | Trunk]: Add properties to enviroment. 2020-06-11 15:52:41 +00:00
package.json [Monitor Dashboard|Trunk] 2020-06-12 09:34:03 +00:00
prerender.ts [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
server.ts [MOnitor Dashboard|Trunk] 2020-06-12 17:32:41 +00:00
static.paths.ts [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
tsconfig.json [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
webpack.server.config.js [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00

README.md

Angular Universal & Anguar-CLI minimal starter

This demo is built following the Angular-CLI Wiki guide

We're utilizing packages from the Angular Universal @nguniversal repo, such as ng-module-map-ngfactory-loader to enable Lazy Loading.

Static or Dynamic

This repo demonstrates the use of 2 different forms of Server Side Rendering.

Static Also known as "prerendering"

  • Happens at build time
  • Renders your application and replaces the dist index.html with a version rendered at the route /.

Dynamic

  • Happens at runtime
  • Uses ngExpressEngine to render you application on the fly at the requested url.

Installation

  • npm install or yarn

Development (Client-side only rendering)

  • run npm run start which will start ng serve (project served at the standard: localhost:4200)

Production

Depending on whether you're publishing dynamic or static prerendering, run the build command, and then serve up your dist folder assets.

NOTE: To deploy your Static site to a static hosting platform you will have to deploy the dist/browser folder, rather than the usual dist

ie: npm run build:dynamic or npm run build:static. All of the files that need to be served will be found within the /dist folder.

Testing Universal (dynamic or static) builds -Locally-

Dynamic : npm run start:dynamic

Compiles your application and spins up a Node Express to dynamically serve your Universal application on http://localhost:4000.

Static : npm run start:static

  • Compiles your application and prerenders your applications files, spinning up a demo http-server so you can view it on http://127.0.0.1:8080