MaDgIK
/
explore-services
13
0
Fork 0
Code Issues Pull Requests Projects Releases 22 Wiki Activity
explore-services/explore
History
konstantina.galouni 33a54b02a6 [Trunk|Explore]: 
1. home.component: 'link' parameter for searchForm.component changed from 'true' to the value of the link.
2. env-properties.json: 'environment' property changed from 'beta' to 'development'.


git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-services-portal/trunk@55221 d315682c-612b-4755-9ff5-7f18f6832af3
 		2019-04-08 12:15:10 +00:00
..
deploy [Trunk] 2019-03-01 11:51:58 +00:00
src [Trunk|Explore]: 2019-04-08 12:15:10 +00:00
.angular-cli.json Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
README.md Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
installOpenaireLib.sh Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
package.json Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
prerender.ts Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
server.ts [Trunk] 2019-03-01 11:51:58 +00:00
static.paths.ts Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
tsconfig.json Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +00:00
webpack.server.config.js Clean up uoa-services-portal/trunk 2018-12-13 12:31:33 +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