https://github.com/luhmann/daenen-next

The webpage of daenen4.de powered by next.js
https://github.com/luhmann/daenen-next

react ssr zeit

Last synced: about 1 month ago
JSON representation

The webpage of daenen4.de powered by next.js

• Host: GitHub
• URL: https://github.com/luhmann/daenen-next
• Owner: luhmann
• Created: 2017-06-07T15:04:24.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2020-09-09T12:02:15.000Z (over 4 years ago)
• Last Synced: 2024-10-24T16:49:13.690Z (6 months ago)
• Topics: react, ssr, zeit
• Language: TypeScript
• Size: 958 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# daenen-next [![Build Status](https://travis-ci.org/luhmann/daenen-next.svg?branch=master)](https://travis-ci.org/luhmann/daenen-next)

[![Greenkeeper badge](https://badges.greenkeeper.io/luhmann/daenen-next.svg)](https://greenkeeper.io/)

The react-powered webpage of [daenen4.de](http://www.daenen4.de) based on [next.js](https://github.com/zeit/next.js/)

## Usage

1.  Make sure you have nvm installed. http://nvm.sh

2.  Switch to correct node version: `$ nvm install`

3.  Install dependencies: `$ npm install`

4.  Start development server `$ npm run dev`

5.  Open in local browser: `$ open http://localhost:3000`

You now have a fully working local development server. All your changes are hot reloaded instantly.

## Additional NPM-Commands

* `npm run build` - will create a startable distribution of the project. Usually not needed in itself but the basis for turning the app into a static version with `npm run export`

* `npm run export` - will turn the page into static html-pages

* `npm start` - start command for the distribution created by `next build` - not needed

* `npm test` - run the e2e-tests in your local browsers. Development-Server must be running for this to work

* `npm run test:ci` - run the e2e-tests as if on the CI-system in headless chrome. Project must have been exported before.

## Updating Data

All data is held in the `json`-files in the `data`-directory. Take note how the existing data is structured and use it as template for the changes you wish to make.

## Deployment

An updated version is automatically deployed into production whenever you commit into `master`.

Tests are run and will stop you if you break any fundamental functionality, but make sure that things look good. Cloudfront-Caches are automatically purged when you deploy, which after a while costs money, so bundle your commits