/pos-frontend

Frontti partio-ohjelma -sovellukselle

Primary LanguageJavaScript

Partio-ohjelmasovellus frontend

1. Project purpose

TODO

2. Architecture

This frontend application is deployed to an Azure App Service.

3. Development environment

3.1. Prerequisites, and what to do first

Environmental variables

You'll find the proper file for local development from LastPass.

3.2. Run tests

Make sure you have installed all dependencies with yarn and then run yarn test.

Press a in the test window.

3.3. Start the application locally

To start the dev env run yarn start.

PWA capabilities

You can test the service worker only in production mode. In order to test it, run yarn build, followed by e.g. yarn global add serve and serve -s build.

3.4. Version control

When working on a new feature or fixing a bug always create a new branch from the master branch. When the feature or fix is complete create a pull request (from now on PR) for the branch. There should always be at least one or two reviewers for the PR and once the PR has been approved it can be merged to master.

4. Test environment

4.1. Access

TODO The test environment is running here.

4.2. Deployment

Anything pushed to the master branch is automatically deployed to the test environment

4.3. Verifying that a deployment was successful

Make sure the GitHub action successfully completes and test environment is accessible and these things works:

  • TODO

4.3.1. Automated test cases

Tests are automatically run during the GitHub workflow when things are pushed to the master branch.

4.3.2. Manual test cases

TODO

4.4. Rollback

As everything from the master branch is deployed to the test environment the only way to change what is deployed is to push new changes or reverting old commits.

4.5. Logs

TODO

4.6. Monitoring

TODO

5. Production environment

5.1. Access

The production app can be found here and here: https://kompassi.partio.fi/

5.2. Deployment

Create a release in GitHub. Fill out tag version and title and then publish the release.

5.3. Verifying that a deployment was successful

Make sure the GitHub action successfully completes and production environment is accessible and these things works:

  • TODO

5.3.1. Automated test cases

Tests are automatically run in the Github action flow.

5.3.2. Manual test cases

TODO

5.4. Rollback

Fix the release

5.5. Logs

TODO

5.6. Monitoring

TODO

6. Continuous integration

Github Actions is used for CI.

7. More useful information

Useful links and information: https://partio-ohjelma.fi/partio-ohjelma-sovellus/