MaDgIK
/
connect
13
0
Fork 0
Code Issues Pull Requests Projects Releases 14 Wiki Activity
478 Commits 5 Branches 14 Tags 43 MiB
TypeScript 80.7%
HTML 18.4%
Less 0.7%
JavaScript 0.2%
Go to file
argiro.kokogiannaki 632a4556e1 [Connect|Trunk] 
Connect Helper: read community from domain for production

Add extra properties file for real production environment (environment.prop.prod.ts)

Add new piwik ids



git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-connect-portal/trunk@59121 d315682c-612b-4755-9ff5-7f18f6832af3
 		2020-07-15 08:19:35 +00:00
deploy [Connect|Trunk] 2020-05-13 07:57:00 +00:00
src [Connect|Trunk] 2020-07-15 08:19:35 +00:00
README.md An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
angular.json [Connect|Trunk] 2020-06-30 16:00:24 +00:00
package.json [Connect|Trunk] 2020-07-15 08:19:35 +00:00
prerender.ts [Connect|Trunk] 2019-06-03 14:41:57 +00:00
server.ts [Connect | Trunk]: Add properties on enviroment 2020-06-11 15:37:16 +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