Konstantina Galouni
d0fba5ce46
1. contact.component.ts & monitor.component.ts: "properties" as first parameter in methods of helper.service.ts. 2. home.component.ts & learn-how.component.ts & learn-in-depth.component.ts: "properties" as first parameter in methods of helper.service.ts | in methods of helper.service.ts check communityId "monitor". 3. searchFunders.component.ts: "Filter" entity has changed - replace field: "valueIsUnique: false" with "filterType: "checkbox". 4. invite.component.ts: a. "properties" as first parameter in methods of helper.service.ts b. create request path in service email.service.ts 5. subscribe.component.ts: Do not reveal users' (subscribers') emails: a. Use new methods "isSubscribedToCommunity()", "subscribeToCommunity", "unSubscribeToCommunity" without email parameter (subscribe.service). b. Use new method "notifyForNewManagers()" when more appropriate than "sendEmail()". git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-monitor-portal/trunk/monitor@58688 d315682c-612b-4755-9ff5-7f18f6832af3 |
||
---|---|---|
deploy | ||
src | ||
README.md | ||
angular.json | ||
package.json | ||
prerender.ts | ||
server.ts | ||
static.paths.ts | ||
tsconfig.json | ||
webpack.server.config.js |
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
oryarn
Development (Client-side only rendering)
- run
npm run start
which will startng 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 usualdist
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