explore-services/explore
argiro.kokogiannaki 4e2eb8f8ed Charts - Iframes:
explore-custom.css: add css for iframecontainer



git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-services-portal/trunk@57017 d315682c-612b-4755-9ff5-7f18f6832af3
2019-09-10 11:48:21 +00:00
..
deploy Charts - Iframes: 2019-09-10 11:48:21 +00:00
src Charts - Iframes: 2019-09-10 11:48:21 +00:00
README.md Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
angular.json [Explore|Trunk] 2019-08-28 09:59:31 +00:00
installOpenaireLib.sh Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
package.json [Explore|Trunk] 2019-06-03 13:21:49 +00:00
prerender.ts [Explore|Trunk] 2019-06-03 13:21:49 +00:00
routes.ts [Trunk|Explore]: 1. Modify prometheus usage: Remove counters and a routes variable. 2. Create a Counter and a Histogram with label route. 3. At every request of a route, counter with label the specific route is increased by 1 and latency is observed at Histogram with the same logic. 2019-06-10 08:48:37 +00:00
server.ts [Explore|Trunk]: Change Buckets for prometheus. 2019-06-18 11:32:16 +00:00
static.paths.ts Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
tsconfig.json [Explore|Trunk] 2019-06-03 13:21:49 +00:00
webpack.server.config.js [Trunk | Explore]: Merging branch "mergeResultLandingPages" into Trunk 56952:56970 2019-09-05 09:01:24 +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