lego-webapp
Open source frontend for abakus.no
Issues: We track issues in the main repo of LEGO
Quick access
Quick Start
$ yarn # Install dependencies
$ yarn start:staging # Start webserver with development backendEverything should be up and running on localhost:3000. The :staging suffix points the webserver at a hosted development backend.
Running with local backend
First, you need to have the django backend running, see webkom/lego.
$ yarn start # Start webserver with local backendServer side rendering (Optional)
In production (live) we use server side rendering. Due to bad hot reloading, we don't use it by default in dev. The server side renderer can be started by running:
$ yarn build
$ yarn ssr # or yarn ssr:stagingEnvironment Variables
The webserver running the frontend can take many optional environment variables. Docs can be found at config/environment.md, and default can be found at server/env.js and config/env.js.
Development
We use some conventions and tools for our JavaScript/React development.
- prettier for JS code formatter.
yarn prettier
- eslint for finding and fixing problems in your JavaScript code.
yarn lint
- flow as a static type checker for JavaScript.
yarn flow
We recommend getting plugins/extensions in VSCode or Vim so the code auto-formats, and automatically prompts you with errors. When you submit code to Github the CI server will automatically run all the commands above to check that your code is up to par.
Unit tests
Unit tests (jest)
Run all the tests and check for lint errors with the command:
$ yarn testFor development you can run the tests continuously by using:
$ yarn test:watchA coverage report can be generated by running yarn test -- --coverage.
Cypress E2E (End-to-end tests)
End to end tests (cypress)
In order to run end to end tests, you need to run both lego-webapp and lego. Lego can be found here: https://github.com/webkom/lego. Lego is assumed to have a clean development database, follow the steps below to achieve that.
Backend
$ cd ../lego
$ docker-compose up -d # Start all services that lego depends on
$ python manage.py initialize_development # Initialize and load data sources (postgres)
$ docker-compose restart lego_cypress_helper # The cypress helper resets database between every test and might need this restart to function correctly
$ python manage.py runserverIf you already have the backend setup, make sure your database is clean
python manage.py reset_db
python manage.py migrate
python manage.py load_fixtures
docker-compose restart lego_cypress_helper # Make sure the copy is of the clean databaseFrontend
Start up the node server
$ yarn startAnd start cypress in another terminal
$ yarn cypress openAlternative: You can also run the node server with server side rendering enabled. This is how the tests are run on CI. To do this, you build and start the server
$ yarn build
$ yarn ssrAnd you run cypress headlessly (no visible browser) in another terminal
yarn cypress runSTRIPE
In order to run the payment end-2-end tests, a few extra steps are required. First one has to install the stripe cli, log in and then run
$ stripe listen --forward-to localhost:8000/api/v1/webhooks-stripe/In addition, the backend needs to run with two environment variables.
$ STRIPE_WEBHOOK_SECRET=<SECRET> STRIPE_TEST_KEY=<SECRET> python manage.py runserverThe webhook is obtained when running the stripe command above, while the test key can be obtained from the stripe dashboard.
Lastly, one has to run the frontend without captcha:
$ SKIP_CAPTCHA=TRUE yarn startDebugging
Debugging
To debug chunk size (size of the javascript sent to the browser), run
$ BUNDLE_ANALYZER=true yarn buildCI/CD
CI/CD
We use drone as our CI/CD system. The server runs at https://ci.webkom.dev. This repo is public, so anyone can see the status at https://ci.webkom.dev/webkom/lego-webapp.
Since the repo is public and we use a lot of secrets in the pipeline, we require the pipeline to be verified with a signature from drone. To obtain this, use the cli:
drone sign webkom/lego-webappYou need to login to retrieve the signature. Get the login data from your user settings.