MaDgIK
/
explore-services
13
0
Fork 0
Code Issues Pull Requests Projects Releases 23 Wiki Activity
explore-services/explore
History
argiro.kokogiannaki d2ef31eab9 [Explore | Trunk] 
update test properties:
	-add portal type
	-update search url (https version)


git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-services-portal/trunk@59498 d315682c-612b-4755-9ff5-7f18f6832af3
 		2020-10-01 11:31:33 +00:00
..
deploy [Explore|Trunk] 2020-09-18 14:02:48 +00:00
src [Explore | Trunk] 2020-10-01 11:31:33 +00:00
README.md Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
angular.json [Explore|Trunk] 2020-08-17 09:12:54 +00:00
installOpenaireLib.sh Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
package.json [Explore|Trunk] 2020-08-17 09:12:54 +00:00
prerender.ts [Explore|Trunk] 2019-06-03 13:21:49 +00:00
routes.ts [Explore | Trunk]: Add new routes to prometheus 2020-04-02 09:21:18 +00:00
server.ts [Explore|Trunk] 2020-04-28 11:10:08 +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