Finalize local dev env setup

.gitattributes

@@ -7,3 +7,4 @@
 *.json text eol=lf
 **/s2i/bin/* text eol=lf
 **/root/**/* text eol=lf
+/docker/manage text eol=lf

.gitignore

@@ -1,5 +1,5 @@
 # Visual Studio Code
-.vscode
+.vscode/tasks.json
 
 ## Ignore Visual Studio temporary files, build results, and
 ## files generated by popular Visual Studio add-ons.

.vscode/launch.json

@@ -0,0 +1,20 @@
+{
+  "configurations": [
+    {
+      "name": ".NET Core Docker Attach",
+      "type": "coreclr",
+      "request": "attach",
+      "processId": "${command:pickRemoteProcess}",
+      "pipeTransport": {
+        "pipeProgram": "docker",
+        "pipeArgs": ["exec", "-i", "scv-api-1"],
+        "debuggerPath": "/vsdbg/vsdbg",
+        "pipeCwd": "${workspaceRoot}",
+        "quoteArgs": false
+      },
+      "sourceFileMap": {
+        "/opt/app-root/src": "${workspaceRoot}/"
+      }
+    }
+  ]
+}

README.md

@@ -21,7 +21,7 @@ The OpenShift build and deployment configurations for the project can be found h
 
 For high level View API documentation refer to the diagram above.  For details, refer to the [router](./web/src/router/index.ts) and [view components](./web/src/components/) source code.
 
-For backend API documentation refer to the Swagger API documentation page available at the `api/` endpoint of the running application.  For example, if you are running the application locally in docker, the Swagger page can be found at https://localhost:8080/scjscv/api/.  Refer to [Running in Docker](#running-in-docker) section for details.
+For backend API documentation refer to the Swagger API documentation page available at the `api/` endpoint of the running application.  For example, if you are running the application locally in docker, the Swagger page can be found at https://localhost:8080/jasper/api/.  Refer to [Running in Docker](#running-in-docker) section for details.
 
 ## Getting Help or Reporting an Issue
 

docker/README.md

@@ -1,10 +1,50 @@
+# Running the Application on DevContainer for Local Development
+
+Hot reloading is configured in both frontend and backend so developers can see the effects of the code changes almost instantly without having to completely restart the application. This significantly speeds up the development process.
+
+## Pre-requisite
+
+Ensure `Docker` and `Dev Containers` extenion (`ms-vscode-remote.remote-containers`) is installed in your machine.
+
+## Steps
+
+1. Launch code in VSCode.
+2. Hit `Ctrl + Shift + P`, select `Dev Containers: Open Folder in Container...` and wait for it to completely load.
+3. Building the project.
+
+```
+./manage build
+```
+
+4. Starting the project.
+
+```
+./manage debug
+```
+
+## Notes
+
+- DevContainer will fail to build/rebuild when connected to the BC Gov's VPN.
+
+- You may find this command handy when wiping all unused containers, volumes, networks and images.
+    ```
+    docker system prune -a --volumes
+    ```
+
+## Using the Application
+
+- By default, the main developer UI is exposed at; https://localhost:8080/
+- The Swagger API and documentation is available at; https://localhost:8080/api/
+- Which is also exposed directly at; http://localhost:5000/api/
+
 # Running the Application on Docker
 
 ## Management Script
 
 The `manage` script wraps the Docker process in easy to use commands.
 
 To get full usage information on the script, run:
+
 ```
 ./manage -h
 ```
@@ -14,34 +54,37 @@ To get full usage information on the script, run:
 The first thing you'll need to do is build the Docker images.
 
 To build the images, run:
+
 ```
 ./manage build
 ```
 
 ## Starting the Project
 
 To start the project, run:
+
 ```
 ./manage start
 ```
 
-This will start the project interactively; with all of the logs being written to the command line.  Press `Ctrl-C` to shut down the services from the same shell window.
+This will start the project interactively; with all of the logs being written to the command line. Press `Ctrl-C` to shut down the services from the same shell window.
 
 Any environment variables containing settings, configuration, or secrets can be placed in a `.env` file in the `docker` folder and they will automatically be picked up and loaded by the `./manage` script when you start the application.
 
 ## Stopping the Project
 
 To stop the project, run:
+
 ```
 ./manage stop
 ```
 
-This will shut down and clean up all of the containers in the project.  This is a non-destructive process.  The containers are not deleted so they will be reused the next time you run start.
+This will shut down and clean up all of the containers in the project. This is a non-destructive process. The containers are not deleted so they will be reused the next time you run start.
 
-Since the services are started interactively, you will have to issue this command from another shell window.  This command can also be run after shutting down the services using the `Ctrl-C` method to clean up any services that may not have shutdown correctly.
+Since the services are started interactively, you will have to issue this command from another shell window. This command can also be run after shutting down the services using the `Ctrl-C` method to clean up any services that may not have shutdown correctly.
 
 ## Using the Application
 
-- By default, the main developer UI is exposed at; https://localhost:8080/scjscv/
-- The Swagger API and documentation is available at; https://localhost:8080/scjscv/api/
-  - Which is also exposed directly at; http://localhost:5000/api/
+- By default, the main developer UI is exposed at; https://localhost:8080/jasper/
+- The Swagger API and documentation is available at; https://localhost:8080/jasper/api/
+- Which is also exposed directly at; http://localhost:5000/api/

docker/api/Dockerfile.dev

@@ -6,4 +6,4 @@ ENV CORS_DOMAIN='http://localhost:8080'
 ENV DOTNET_STARTUP_PROJECT='./api/api.csproj'
 ENV DOTNET_USE_POLLING_FILE_WATCHER 1
 
-RUN    curl -sSL https://aka.ms/getvsdbgsh | /bin/sh /dev/stdin -v latest -l /vsdbg
+RUN curl -sSL https://aka.ms/getvsdbgsh | /bin/sh /dev/stdin -v latest -l /vsdbg

docker/docker-compose.yaml

@@ -2,7 +2,7 @@ version: "3.4"
 services:
 
   web:
-    image: scv-web
+    image: "${COMPOSE_PROJECT_NAME}-web"
     environment:
       - API_URL=${API_URL}
       - USE_SELF_SIGNED_SSL=${USE_SELF_SIGNED_SSL}
@@ -15,9 +15,26 @@ services:
     depends_on:
       - api
 
+  web-dev:
+    image: "${COMPOSE_PROJECT_NAME}-web-dev"
+    environment:
+      - API_URL=${API_URL}
+      - WEB_BASE_HREF=${WEB_BASE_HREF}
+      - DEV_MODE=false
+      - NODE_ENV=development
+      - NPM_CONFIG_LOGLEVEL=notice
+      - NPM_RUN=serve
+    ports:
+      - 8080:1339
+    volumes:
+      - "../web/src:/opt/app-root/src/src"
+      - "../web/package.json:/opt/app-root/src/package.json"
+    depends_on:
+      - api
+
   api:
-    image: scv-api
-    environment: 
+    image: "${COMPOSE_PROJECT_NAME}-api"
+    environment:
       - ASPNETCORE_URLS=${ASPNETCORE_URLS}
       - FileServicesClient__Username=${FileServicesClientUsername}
       - FileServicesClient__Password=${FileServicesClientPassword}
@@ -56,8 +73,8 @@ services:
       - ../api/:/opt/app-root/src/api
       - ../db/:/opt/app-root/src/db
       - ../jc-interface-client/:/opt/app-root/src/jc-interface-client
-      - scv-api-dev-bin:/opt/app-root/src/api/bin
-      - scv-api-dev-obj:/opt/app-root/src/api/obj
+      - api-dev-bin:/opt/app-root/src/api/bin
+      - api-dev-obj:/opt/app-root/src/api/obj
       - ./seed:/opt/app-root/data
     depends_on:
       - db
@@ -80,5 +97,5 @@ services:
       - ./tmp:/tmp2
 
 volumes:
-  scv-api-dev-bin:
-  scv-api-dev-obj:
+  api-dev-bin:
+  api-dev-obj: