hrasoa/react-pwa

Real world progressive web application starter-kit

React Progressive Web Application

⏳ In progress

Real world progressive web application starter-kit running with an Ingress controller, a Nginx reverse proxy and pm2 on production:

🌍 ➡️ Ingress ➡️ Nginx ➡️ App

Stack

docker kubernetes nginx pm2 redis (sessions storage) express mysql graphql webpack react redux redux-saga firebase workboxjs

Features

	Development	Production
Hot Module Replacement	⭐
GraphiQL	⭐
Code Split + Async Components	⭐	⭐
Server Side Rendering	⭐	⭐
Service Worker (precache, offline)		⭐
Long term caching		⭐
Minify + gzip		⭐

Prerequisites

• docker-compose
• docker-sync (optional)

Getting started

$ git clone [email protected]:hrasoa/react-pwa.git app
$ cd app/docker
$ docker-sync start

# init the db instance
$ docker-compose run --rm db

# in a new tab stop the containers after finished
$ docker stop $(docker ps -q --filter "ancestor=mysql")   

# install the app
$ docker-compose run --rm --no-deps app yarn

# run
$ docker-compose up

Visit http://localhost:8001

Running the production build:

$ docker-compose run --rm --no-deps app npm run build:production
$ docker-compose -f docker-compose.yml -f production.yml up    

Deployment

This app will work out of the box on Google Cloud Platform with Jenkins CI Multi-branch Pipeline, more information in the Jenkinsfile.

You can follow this tutorial to setup your continuous delivery pipeline.

License

MIT

react-pwa's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.