Local and Prod Separation

[mmad4804]

I made some changes to the project structure so that it can once again be run locally for testing separate from the production instance. I modified parts of the workflow so that the variables are inserted dynamically so that it can still work on our production instance.

To test this:
You will need to update your .env file. Follow the example in the new .env.example file I created. To generate your own AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID:

1. Go to the AWS Management Console and navigate to IAM.
2. Click on 'Users' within the left-hand menu and click on your email/account.
3. Navigate to the 'Security credentials' tab and scroll down to the section titled Access Keys. Click 'Create access key'.
4. Select 'Application running outside AWS'. Click 'Create access key' again.
5. CRITICAL: Copy both the Access key ID and Secret access key immediately to paste into your .env file, because once you navigate away from the page you won't be able to access them anymore.

Once your .env file is configured, you can open and run the following three terminals to test locally:

• npm run proxy
• npm run dev
• pico-engine