MaDgIK
/
monitor
13
0
Fork 0
Code Issues Pull Requests Projects Releases 12 Wiki Activity
1 Commit 2 Branches 12 Tags 39 MiB
TypeScript 68.9%
HTML 28.2%
Less 2.1%
JavaScript 0.8%
Go to file
Argiro Kokogiannaki dd76c389ac Update the structure of the project 
add funder and initiatives pages
update the home page
css updates



git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-monitor-portal/trunk/monitor@54549 d315682c-612b-4755-9ff5-7f18f6832af3
 		2019-01-09 11:05:23 +00:00
deploy Update the structure of the project 2019-01-09 11:05:23 +00:00
src Update the structure of the project 2019-01-09 11:05:23 +00:00
.angular-cli.json Update the structure of the project 2019-01-09 11:05:23 +00:00
README.md Update the structure of the project 2019-01-09 11:05:23 +00:00
package.json Update the structure of the project 2019-01-09 11:05:23 +00:00
prerender.ts Update the structure of the project 2019-01-09 11:05:23 +00:00
server.ts Update the structure of the project 2019-01-09 11:05:23 +00:00
static.paths.ts Update the structure of the project 2019-01-09 11:05:23 +00:00
tsconfig.json Update the structure of the project 2019-01-09 11:05:23 +00:00
webpack.server.config.js Update the structure of the project 2019-01-09 11:05:23 +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