Go to file
Argiro Kokogiannaki 004e5e9766 [Monitor Dashboard|Trunk]
App routing: remove admin menu when not needed
	add  '*pages*' route

App component: 
	set navbar in the middle
	add stakeholder name or title in blue bar when sidebar is closed 

Require login for admin parts
Require admin role for managing pages, entities, helptexts, etc

Monitor Component:
	change acive topic css
	



git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-monitor-portal/trunk/monitor_dashboard@57961 d315682c-612b-4755-9ff5-7f18f6832af3
2020-01-09 14:31:55 +00:00
deploy [Monitor Dashboard]: Add Topic page 2019-11-05 14:59:06 +00:00
src [Monitor Dashboard|Trunk] 2020-01-09 14:31:55 +00:00
README.md [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
angular.json [Monitor Dashboard]: 1. Change inputs to materials. 2. Add fonts. 3. Add uikit.js on index 4. Add reorder functionality on indicators. 5. Fix height of header to 70px 2019-11-26 19:11:24 +00:00
package.json [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
prerender.ts [Monitor_Dashboard|Trunk] 2019-10-24 07:44:29 +00:00
server.ts [Monitor_Dashboard|Trunk] 2019-12-20 11:48:35 +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