feat: update paths and workingdir (#686)

.github/workflows/aws-preview.yml

@@ -25,7 +25,7 @@ jobs:
     runs-on: ubuntu-latest
     defaults:
       run:
-        working-directory: ./backend/core
+        working-directory: ./backend
     environment: production
 
     steps:

.github/workflows/aws.yml

@@ -24,7 +24,7 @@ jobs:
     runs-on: ubuntu-latest
     defaults:
       run:
-        working-directory: ./backend/core
+        working-directory: ./backend
     environment: production
 
     steps:

docs/docs/get_started/intro.md

@@ -77,11 +77,11 @@ Additionally, you'll need a [Supabase](https://supabase.com/) account for:
 - **Step 2**: Copy the `.XXXXX_env` files
 
 ```bash
-cp .backend_env.example backend/.env
+cp .backend_env.example backend/core/.env
 cp .frontend_env.example frontend/.env
 ```
 
-- **Step 3**: Update the `backend/.env` and `frontend/.env` file 
+- **Step 3**: Update the `backend/core/.env` and `frontend/.env` file 
 
 > _Your `supabase_service_key` can be found in your Supabase dashboard under Project Settings -> API. Use the `anon` `public` key found in the `Project API keys` section._
 
@@ -90,7 +90,7 @@ cp .frontend_env.example frontend/.env
 
 > _To activate vertexAI with PaLM from GCP follow the instructions [here](https://python.langchain.com/en/latest/modules/models/llms/integrations/google_vertex_ai_palm.html) and update `backend/.env`- It is an advanced feature, please be expert in GCP before trying to use it_
 
-- [ ] Change variables in `backend/.env`
+- [ ] Change variables in `backend/core/.env`
 - [ ] Change variables in `frontend/.env`
 
 - **Step 4**: Run the following migration scripts on the Supabase database via the web interface (SQL Editor -> `New query`)