Mobile App without Device Testing using AWS Device farm

Part 1: Create the project

1. Open AWS Device Farm.

2. On the left menu, look for Mobile Device Testing.

3. Select Projects.

4. Click Create a new project.

5. Enter:

Project_name Enterprise QA

6. Click Create project.

If you cannot see Projects, click the ☰ menu in the upper-left corner.

Part 2: Start an Android remote session

Inside the newly created project:

1. Open the Remote access tab.

2. Click Start a new session.

3. Enter a session name such as:

Project_name Android Smoke Test

4. Under device selection, select Android.

5. Initially choose one commonly used device, such as:

Samsung Galaxy S23/S24
Google Pixel 7/8

6. Choose a stable Android version supported by the project app.

7. Select an available device.

8. Click Confirm and start session or Start session.

AWS may take several minutes to prepare the physical device.

Billing normally starts when the device session begins. Do not leave the session running unnecessarily.

Part 3: Upload and install the APK

When the remote Android device appears:

1. Find Install application, Upload application, or the upload icon.

2. Select:

project_name.apk

3. Wait for AWS to upload and install it.

4. Open Medicalin from the device.

5. Perform this initial smoke test:

• App installs successfully

• App opens without crashing

• Logo and first screen display correctly

• Login page loads

• Test account can log in

• Dashboard loads

• Basic navigation works

• Logout works

• No obvious layout problems

• Backend connection succeeds

Take screenshots of any errors. AWS should also provide device logs and session information.

Part 4: End the Android session

When testing is complete:

1. Click End session or Stop session.

2. Confirm the session has ended.

3. Record:

Device:
Android version:
APK version:
Installation: Pass/Fail
Launch: Pass/Fail
Login: Pass/Fail
Issues:
Session ID:

Ending it is important because Device Farm charges by device minute after the free allowance. AWS currently advertises a one-time 1,000-device-minute free trial, followed by $0.17 per device minute. AWS Device Farm pricing

Part 5: Test the iOS IPA

Return to your project:

1. Open Remote access.

2. Click Start a new session.

3. Name it:

Project_name iOS Smoke Test

4. Select iOS.

5. Choose an available iPhone.

6. Prefer an iOS version supported by the project.

7. Start the session.

8. When the iPhone is ready, choose Install application.

9. Upload:

project_name.ipa

10. Wait for installation and launch the app.

11. Repeat the same login and navigation checks.

12. End the session immediately after testing.

If AWS rejects the IPA, copy the exact error. Common causes include:

• Invalid or incomplete code signing

• Unsupported provisioning

• Missing application entitlements

• IPA built for the simulator instead of a physical iPhone

• Corrupted IPA package

The development team may need to produce a new physical-device .ipa.

If you receive “Access denied”

Your AWS user may need Device Farm permissions. For initial testing, the administrator can attach:

AWSDeviceFarmFullAccess

A restricted custom policy is safer for long-term use, but the managed policy is simpler for the first controlled test.

Integrate Sentry with AI Agents

 To get Sentry set up for production error tracking:

1. Create a Sentry project
- Sign up at [sentry.io](https://sentry.io) (free tier covers most apps)
- Create an organization and a React project
- Note these three values:
  - SENTRY_ORG — your org slug (from the URL: `https://<org>.sentry.io`)
  - SENTRY_PROJECT — the project slug
  - SENTRY_AUTH_TOKEN — Settings → Auth Tokens (Organization Tokens). Just click "Create New  (needs `project:releases` and `org:read` scopes)

2. Add them to your AI developer Agent
Add these as Build Secrets in your workspace:
- Go to Workspace Settings → Build Secrets
- Add `SENTRY_AUTH_TOKEN`, `SENTRY_ORG`, and `SENTRY_PROJECT`
- These are injected during `bun run build`, so the source-map upload plugin can authenticate

3. About “automatically fixing errors”
Sentry does not auto-fix code by itself. What it can do:
- Capture errors with stack traces, release version, and user context
- Group similar errors and alert you
- The AI developer Agent Sentry MCP connector can read Sentry issues inside chat and help investigate root causes
- AI developer Agent can then propose and implement fixes based on that investigation

So the workflow is: error appears in Sentry → AI developer Agent connector surfaces it → you or a developer asks AI developer Agent to investigate → AI developer Agent proposes a fix → you approve and it lands in the codebase.

Steps To Install Python locally

Install Python

Go to https://www.python.org/downloads/

Click "Download Python 3.x.x" (latest version)

Run the installer — IMPORTANT: check "Add python.exe to PATH" before clicking Install

Steps to do email forwarding in a microsoft user account

 

.

Use the Exchange Admin Center directly

Since you have Exchange Admin rights, do this instead:

1. Open:

   https://admin.exchange.microsoft.com
   

2. Go to:

   Recipients → Mailboxes
   

3. Select Test Name (name@test.com).

4. Click:

   Mail flow settings
   

5. Choose:

   Email forwarding
   

6. Turn forwarding ON.

7. Enter:

   admin@test.com
   

8. IMPORTANT: Uncheck:

   Deliver message to both forwarding address and mailbox
   

   This ensures:

   • ✅ Admin receives the email.

   • ❌ User no longer receives a copy.

9. Click Save.

SUPABASE Commands

Command to run migration files from code to  create db in the supabase 

 

cd /var/www/html/project_name

supabase link --project-ref supabase_id
supabase db push

----------------------------------------

Command to deploy the functions from code to the supabase

--------------------------------------------
supabase functions deploy --project-ref supabase_id
 

Install and setup POSTGRESQL DB in ubuntu

1) Install POSTGRESQL 

sudo apt update

sudo apt install -y postgresql postgresql-contrib

2) Verify it is working

sudo systemctl status postgresql

3) setup DB

sudo -u postgres psql

4) CREATE USER user_name WITH PASSWORD 'password';

CREATE DATABASE name_db OWNER user_name;

GRANT ALL PRIVILEGES ON DATABASE name_db TO user_name;

\q

How to move servers between AWS regions

Step 1 — Create AMI in Source Region

In AWS console:

EC2 → Instances
Select your instance
Actions → Image and templates → Create Image

Wait until AMI is ready.

---

Step 2 — Copy AMI to Destination region

Go to:

EC2 → AMIs
Select AMI
Actions → Copy AMI
Destination region → US East (N. Virginia)

---

Step 3 — Launch new instance

Switch region to N. Virginia

EC2 → AMIs → Launch instance

Your server will start in us-east-1.

---

Important: IP address will change

You will get a new public IP, which we can  configure it in our DNS.

Allocate swap file, when server RAM GB is low to remove mysql errors

 sudo fallocate -l 2G /swapfile || sudo dd if=/dev/zero of=/swapfile bs=1M count=2048
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

# optional but recommended
echo 'vm.swappiness=20' | sudo tee /etc/sysctl.d/99-swappiness.conf
sudo sysctl -p /etc/sysctl.d/99-swappiness.conf

free -h
swapon --show

cPanel multi-domain hosting for laravel project

 STEP 1 — Create the Subdomain

                    cPanel → Domains → Create A New Domain (or Subdomains)

cPanel will automatically create:

/home/egproject/test.example.com/

STEP 2 — Correct Laravel Folder Structure (Very Important)

/home/egproject/

    test/                             ← FULL Laravel project

   test.example.com/        ← ONLY public folder contents

STEP 3 — Upload Files Properly

1️⃣ Upload full project here:

/home/egproject/test/

         

app/

bootstrap/

config/

database/

public/

resources/

routes/

storage/

vendor/

.env

artisan

2️⃣ Now open:

/home/egproject/test/public/

Copy EVERYTHING inside public folder to:

/home/egproject/test.example.com/

So that folder contains:

index.php

.htaccess

css/

js/

images/

 STEP 4 — Modify index.php (CRITICAL)

/home/egproject/test.example.com/index.php

Change these lines:

FROM:

require __DIR__.'/../vendor/autoload.php';
$app = require_once __DIR__.'/../bootstrap/app.php';

TO:

require __DIR__.'/../test/vendor/autoload.php';
$app = require_once __DIR__.'/../test/bootstrap/app.php';

Because your Laravel core lives in /test.

STEP 5 — Update .env

APP_URL=https://test.example.com

DB_HOST=localhost

DB_DATABASE=egproject_db

DB_USERNAME=egproject_user

DB_PASSWORD=yourpassword

STEP 6 — Permissions (Very Important)

In File Manager:

Set:

test/storage → 755
test/bootstrap/cache → 755

If errors:

chmod -R 775 storage
chmod -R 775 bootstrap/cache

STEP 7 — Set up database

    cPanel → Database Manager → Create DB and setup user for that

How to allow higher MB file uploads by increasing size in server php.ini

1) Check php version using the command:

                            php -v

2) Make sure server is using apache php or php cli by using the below command

                        sudo systemctl status

3) Check if any php-fpm is running. else

            sudo nano  /etc/php/8.4/cli/php.ini

4) Edit php.ini and change these values from 2M to 10 or 20 M

                    upload_max_filesize = 10M 

                    post_max_size = 10M

4. Restart web server:

                    sudo systemctl restart php8.4-fpm

                     sudo systemctl restart apache2

Get Gmail App Password for email notification through laravel app

 

First, you need to create an App Password from your Google Account:

    Go to your Google Account: https://myaccount.google.com/

    Click on "Security" in the left menu

    Enable "2-Step Verification" if not already enabled

    Go back to Security → 2-Step Verification

    Scroll down to "App passwords"

    Select "Mail" and "Other (Custom name)"

    Enter a name like "Laravel App"

    Click "Generate"

    Copy the 16-character password (no spaces)

     

     Update .env file with the following info:

MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=587
MAIL_USERNAME=your-email@gmail.com
MAIL_PASSWORD=your-16-char-app-password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS="your-email@gmail.com"
MAIL_FROM_NAME="${APP_NAME}"

     

     

     

     

How to change git origin for repo after making a copy of the repo

 1) Locally  run the following commands for the existing repo:

                        git remote -v

This will help us find the current remote origin

2) Set remote origin to the new repo:

                    git remote set-url origin git@gitlab.com:folder/repo.git

3) Locally ensure that it is in the correct branch

                    git checkout import-main

4) if activities were done in a new branch, merge it with the current branch "import main"

                                                  git merge main

5) push the code to the git

                        git push

Create a basic Sharepoint communication Site for your company

✅ Step-by-step: Build MyCompany SharePoint Internal Hub

Step 0 — Decide Names (use these)

• Hub site: MyCompany Central Hub
• Sites: Operations, IT & Systems, Sales & Marketing, Finance, Compliance & Legal, Events & CME

---

1️⃣ Create the Main Hub Site (Central Portal)

1. Go to: Microsoft 365 → App Launcher (9 dots) → SharePoint
2. Click: Create site
3. Choose: Communication site
4. Select a template: Blank (best) or Topic
5. Site name: MyCompany Central Hub
6. Click Finish

✅ This becomes your main landing page.

---

2️⃣ Register it as a Hub Site (Admin Step)

1. Open: SharePoint Admin Center

1.      Go to https://admin.microsoft.com

2.      Select Admin centers → SharePoint

2. Go to: Sites → Active sites
3. Find and select: MyCompany Central Hub
4. Click: Hub → Register as hub site
5. Hub name: MyCompany Central Hub
6. Save

✅ Now you can manage global navigation + consistent branding.

---

3️⃣ Create Department Sites (Communication Sites)

Repeat these steps for each department:

1. In SharePoint home → Create site
2. Choose: Communication site
3. Name: MyCompany Operations
4. Finish

Create these sites:

• MyCompany Operations
• MyCompany IT & Systems
• MyCompany Sales & Marketing
• MyCompany Finance
• MyCompany Compliance & Legal
• MyCompany Events & CME

---

4️⃣ Connect Each Site to the Hub (Very important)

For each department site:

1. Open the department site
2. Click: Settings (⚙️) → Site information
3. Look for: Hub site association
4. Select: MyCompany Central Hub
5. Save

✅ Now all sites share the same top navigation style and theme.

---

5️⃣ Build the Top Menu (Hub Navigation)

1. Open: MyCompany Central Hub
2. At top menu, click: Edit
3. Add links (one by one):

·  Click ➕ Add link

4.      · 

• Operations → link to Operations site
• IT & Systems → link to IT site
• Sales & Marketing → link to Sales site
• Finance → link to Finance site
• Compliance & Legal → link to Compliance site
• Events & CME → link to Events site
4. Click: Save

✅ This gives you the “AIU-style” department navigation.

---

6️⃣ Create the Hub Home Page Layout

A) Add the Banner

1. On hub home → click Edit
2. Click + → add Hero Web Part
3. Choose layout: Layered
4. Add a banner image (brand/medical theme)
5. Title: MyCompany Central Hub
6. Subtitle: Internal Operations & Systems Portal

B) Add Quick Action Buttons (right side feel)

1. Click + under the banner area
2. Add Quick Links
3. Layout: Buttons
4. Add buttons:
• SOPs & Policies
• IT Support Request
• Finance Requests
• Compliance Docs
• CME & Events
5. Publish the page

---

7️⃣ Create Document Libraries (Core of SharePoint)

Go to each department site and create libraries:

Operations site:

• SOPs & Policies
• Templates
• Reports

IT & Systems site:

• System Documentation
• Deployment Notes
• Change Requests (List, not library)

Finance site:

• Invoices
• Budgets
• Vendor Payments

Compliance site:

• Contracts
• Regulatory Docs
• Audit Records

Events & CME:

• Event Planning
• Post-Event Reports
• Marketing Assets

How to create a library:

1. Go to the site → New → Document library
2. Name it
3. Create

---

8️⃣ Create Lists for Requests (Forms replacement)

A) IT Support Request List

1. Go to IT site
2. Click New → List
3. Choose Blank list
4. Name: IT Support Requests
5. Add columns:
• Request Type (Choice)
• Priority (Choice: Low/Med/High/Urgent)
• Requested By (Person)
• Description (Multiple lines)
• Status (Choice: New/In Progress/Done)

B) Operations Requests (Optional)

Same concept for Operations.

---

9️⃣ Setup Permissions (Internal-only)

Since suppliers cannot access, keep it simple:

1. Go to each site → Settings (⚙️) → Site permissions
2. Use standard groups:
• Owners (full control)
• Members (edit)
• Visitors (read)

✅ Recommendation:

• Operations: most staff can read
• IT: only IT team can edit
• Finance/Compliance: restricted access

---

🔟 Turn on Versioning (Very important)

For each document library:

1. Open library → Settings → Library settings
2. Click Versioning settings
3. Enable:
   ✅ Create major versions
   ✅ Keep versions (e.g., 50)

This prevents accidental loss.

---

1️⃣1️⃣ Publish + Test

1. Log in as a normal user (or test account)
2. Confirm they can:
• Open hub
• Navigate sites
• View correct docs
• Not access Finance/Compliance (if restricted)