Go to file
konstantina.galouni 955958a7c8 [Trunk | Connect]:
1. communities.component.ts & contentPage.component.ts & shareInZenodo.component.ts & helper-test.component.ts & organizationsPage.component.ts & 
   learn-how.component.ts & learn-in-depth.component.ts & my-communities.component.ts:
	"properties" as first parameter in methods of helper.service.ts.
2. contact.component.ts & curators.component.ts & invite.component.ts: 
	a. "properties" as first parameter in methods of helper.service.ts
	b. create request path in service (email.service.ts, curator.service.ts).
3. htmlPage.component.ts & htmlPage.service.ts: "properties" as first parameter in methods of htmlPage.service.ts.
4. customization.component.ts: create request path in service (layout.service.ts).
5. subscribe.component.ts: create request path in service (subscribe.service.ts).


git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-connect-portal/trunk@58421 d315682c-612b-4755-9ff5-7f18f6832af3
2020-04-07 16:52:19 +00:00
deploy [Connect|Trunk] 2020-04-03 16:02:40 +00:00
src [Trunk | Connect]: 2020-04-07 16:52:19 +00:00
README.md An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
angular.json Apply changes from Elixir branch r58296 2020-04-06 14:51:22 +00:00
package.json Apply changes from Elixir branch r58296 2020-04-06 14:51:22 +00:00
prerender.ts [Connect|Trunk] 2019-06-03 14:41:57 +00:00
server.ts [connect | Trunk] 2019-11-14 10:12:48 +00:00
static.paths.ts Add Other Research Products: landing page, advanced search,simple search and community page 2018-07-27 14:45:08 +00:00
tsconfig.json [Connect|Trunk] 2019-06-03 14:41:57 +00:00
webpack.server.config.js [Connect|Trunk] 2019-06-03 14:41:57 +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