Merge pull request #86 from manics/working-dirs

Use relative working dirs where possible

doc/deployment/Step4-DeployDataEgressApp.md

@@ -48,7 +48,7 @@ Apply these steps only to accounts that are part of the **TRE Projects Prod** OU
 Log in to the [AWS Management Console](https://console.aws.amazon.com/) using your **TRE Project 1 Prod**
  account and Admin privileges.
 
-- [ ] Edit file [`cdk.json`](../../src/components/egress_app_backend/cdk.json) in the `/home/ec2-user/tmp/TREEHOOSE/src/components/egress_app_backend/` directory (Step 1C). Change the following required
+- [ ] Edit file [`cdk.json`](../../src/components/egress_app_backend/cdk.json) in the `src/components/egress_app_backend/` directory (Step 1C). Change the following required
  parameters for the CDK backend stack:
 
 |Parameter Name|Description|Location|AWS Account|
@@ -66,7 +66,7 @@ Log in to the [AWS Management Console](https://console.aws.amazon.com/) using yo
 - [ ] Run the following commands to create an isolated Python environment and deploy the CDK backend stack, replacing `DEPLOYMENT_ACCOUNT` with TRE Project 1 Prod account ID:
 
 ```bash
-cd /home/ec2-user/tmp/TREEHOOSE/src/components/egress_app_backend/
+cd src/components/egress_app_backend
 alias cdkv1="npx [email protected]"
 python3 -m venv .venv
 source .venv/bin/activate
@@ -84,7 +84,7 @@ Apply these steps only to accounts that are part of the **TRE Projects Prod** OU
 Log in to the [AWS Management Console](https://console.aws.amazon.com/) using your **TRE Project 1 Prod**
  account and Admin privileges.
 
-- [ ] Edit file [`.env.local`](../../src/components/egress_app_frontend/.env.local) in the `/home/ec2-user/tmp/TREEHOOSE/src/components/egress_app_frontend/` directory (Step 1C). Change the following required
+- [ ] Edit file [`.env.local`](../../src/components/egress_app_frontend/.env.local) in the `src/components/egress_app_frontend` directory (Step 1C). Change the following required
  parameters for the web application:
 
 |Parameter Name|Description|Location|AWS Account|
@@ -101,7 +101,7 @@ Log in to the [AWS Management Console](https://console.aws.amazon.com/) using yo
 - [ ] Run the following commands to build the React frontend code:
 
 ```bash
-cd /home/ec2-user/tmp/TREEHOOSE/src/components/egress_app_frontend/
+cd src/components/egress_app_frontend
 nvm install v16.15.0
 nvm use v16.15.0
 npm install
@@ -111,15 +111,15 @@ npm run build
 - [ ] Run the following commands to build the React app:
 
 ```bash
-cd /home/ec2-user/tmp/TREEHOOSE/src/components/egress_app_frontend/build
+cd build
 zip -r ../build.zip ./
 ```
 
 - [ ] Run the following commands to copy the React app to S3 and trigger an automatic
  deployment to Amplify:
 
 ```bash
-cd /home/ec2-user/tmp/TREEHOOSE/src/components/egress_app_frontend/
+cd ..
 aws s3 cp build.zip s3://{egress web app bucket created in Step 4B}
 ```
 

doc/deployment/Step6-DeployBackupComponent.md

@@ -44,6 +44,8 @@ alias cdk2="npx [email protected]"
 |move_to_cold_storage_after|defines the number of days after which the backup is archived to cold storage|90|AWS Backup for EBS currently does not support this. Uses S3 lifecycle policy for SageMaker backups|
 |sagemaker_enable_selfservice_restore|controls if SageMaker notebook user is able to restore backed-up files|true||
 
+- [ ] Change directory to root folder of the backup component code: `src/components/workspace_backup/`.
+
 - [ ] Run the following commands to create an isolated Python environment, bootstrap and deploy the CDK stack.
       Update DEPLOYMENT_ACCOUNT with the account number where you want to deploy the backup component: