Go to file
konstantina.galouni e083e5f887 1. 'enableSearchView' input parameter added in searchPageTableView.component in library's update.
(When status is not DONE, all forms and search view are disabled. When status is not LOADING or DONE, hide datatable and disable all forms but allow search view)


git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-connect-portal/trunk@52167 d315682c-612b-4755-9ff5-7f18f6832af3
2018-05-23 13:29:07 +00:00
src 1. 'enableSearchView' input parameter added in searchPageTableView.component in library's update. 2018-05-23 13:29:07 +00:00
.angular-cli.json An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
README.md An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
connect-production-properties.json correct admin tools API double slash in prod properties, add prepare deploy script, use the same property for communities API in app component, remove dashboard menu item, comment title & message for dashboard stats 2018-05-23 12:22:14 +00:00
package.json add ngx-json-ld library in package.json - requires install 2018-05-17 12:58:49 +00:00
prepareDeploy.sh correct admin tools API double slash in prod properties, add prepare deploy script, use the same property for communities API in app component, remove dashboard menu item, comment title & message for dashboard stats 2018-05-23 12:22:14 +00:00
prerender.ts An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
server.ts An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
static.paths.ts An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
tsconfig.json An initial commit for Connect portal 2018-01-26 15:00:07 +00:00
webpack.server.config.js An initial commit for Connect portal 2018-01-26 15:00:07 +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