Added manual deployment description

README.md

 # MAT2 Quasar Frontend (PWA)
-
 ![](mat-frontend.gif)
+This is a frontend for [MAT2-web](https://0xacab.org/jvoisin/mat2-web).
 
-## Up and Running
+## Up and Running for development
 To start developing use `docker-comse up` and if
 this was successful you can access the app on: 
 `localhost:8080`. This will start the backend as well
  using it's latest docker image.
 
-## Configuration
+### Configuration
 To set the base url of the backend you have to define
 `MAT2_API_URL_DEV` for dev builds and `MAT2_API_URL_PROD`
 for production builds. If you use the docker environment
 this is customizable in the `docker-compose.yml` file.
 If none of these are set it will default to `http://localhost:5000/` (slash at the end).
 
-## Docker
+## Docker Container Registries for this project
 **Registry Frontend:** https://0xacab.org/jfriedli/mat2-quasar-frontend/container_registry
 **Registry Backend:** https://0xacab.org/jvoisin/mat2-web/container_registry
 
@@ -33,6 +33,18 @@ Or alternatively get it from the registry prebuilt.
 Then run it:
 `docker run -it -e MAT_API_HOST_PLACEHOLDER='https://mybackend.gnu/' -p 80:80 mat2frontend`
 
+## Manual Deployment
+To create a build yourself:
+
+1) Install dependencies: `yarn install`
+2) Export env variable `MAT2_API_URL_PROD` which points to your [MAT2-web backend](https://0xacab.org/jvoisin/mat2-web)
+ e.g. `MAT2_API_URL_PROD=https://mybackend.gnu/`. Alternatively you can define the URL in the `quasar.conf.js` file
+ on the following line: `API_URL: JSON.stringify(process.env.MAT2_API_URL_PROD)` and change it to: 
+ `API_URL: 'https://mybackend.gnu/'`
+3) `quasar build -m pwa` (Must have installed the quasar cli)
+4)  Copy the files from `./dist/pwa` to your hosting.
+5) Enjoy :)
+
 ## Dependency Management
 We do use renovate which checks every night for updates and creates automated merge request.