8ed77aef1e
1. Connect first page: browse-community.component & communities.component & assets/home.jpg: a. Show 'private' and 'subscribed' tags in all cards. b. Show 'manage' button in below (browse) cards too. c. Cut title in 50 characters and description in 150 characters. d. Change home.jpg for better view. e. Queryparam to Communities Search Page for manager changed from 'status: "managing"' to 'role: "manager"'. f. In 'View all' links, add number. g. Bug fix: properly show communities. h. Query if user is subscribed for every community to initialize correctly 'subscribed' tag. i. Sort communities by 'creationDate' and then by 'title'. 2. community-creation-instructions.component: Add piwik service call and set title of the browser tab. git-svn-id: https://svn.driver.research-infrastructures.eu/driver/dnet40/modules/uoa-connect-portal/trunk@55354 d315682c-612b-4755-9ff5-7f18f6832af3 |
||
---|---|---|
deploy | ||
src | ||
.angular-cli.json | ||
README.md | ||
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