MaDgIK
/
eosc-explore
13
0
Fork 0
Code Issues Pull Requests Projects Releases 12 Wiki Activity
16 Commits 9 Branches 12 Tags 6.6 MiB
TypeScript 76.2%
HTML 15.2%
CSS 3.9%
Less 3.5%
JavaScript 1.2%
Go to file
argiro.kokogiannaki fcf246099e [Aggregator|Trunk] 
- use mock admin tool response for enabled entities/ pages
- disable helptexts
- remove unused components
- add again isRoute enabled for claims/ deposit pages



git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-aggregator-portal/trunk@59969 d315682c-612b-4755-9ff5-7f18f6832af3
 		2020-11-25 17:39:05 +00:00
deploy [Trunk] 2019-05-24 13:54:22 +00:00
src [Aggregator|Trunk] 2020-11-25 17:39:05 +00:00
README.md [Aggregator|Trunk] 2019-05-23 12:20:48 +00:00
angular.json [Aggregator | Trunk]: Add material css 2020-11-24 08:47:55 +00:00
package.json [Aggregator |Trunk] 2020-11-18 17:01:52 +00:00
prerender.ts [Aggregator|Trunk] 2019-05-23 12:20:48 +00:00
prometheus.ts [Trunk] 2019-05-28 13:27:12 +00:00
server.ts [Trunk] 2019-05-28 13:27:12 +00:00
static.paths.ts [Aggregator|Trunk] 2019-05-23 12:20:48 +00:00
tsconfig.json [Aggregator|Trunk] 2019-05-23 12:20:48 +00:00
webpack.server.config.js [Aggregator|Trunk] 2019-05-23 12:20:48 +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