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)

 

Set Up PostgreSQL locally in Ubuntu

Install PostgreSQL

 sudo apt update
sudo apt install postgresql postgresql-contrib
sudo systemctl start postgresql

Basic Setup

# Create database and user
sudo -u postgres psql

# In PostgreSQL shell:
CREATE DATABASE myapp;
CREATE USER myuser WITH PASSWORD 'mypassword';
GRANT ALL PRIVILEGES ON DATABASE myapp TO myuser;
\q

Connect

# Command line
psql -h localhost -U myuser -d myapp

# Connection string
postgresql://myuser:mypassword@localhost:5432/myapp

Environment Variables

DATABASE_URL="postgresql://myuser:mypassword@localhost:5432/myapp"

AWS Data Lifecycle Manager (DLM) setup for automated EC2 backups

Step 1: Choose “Custom policy” (as shown)

Keep:

• Custom policy → selected

• Policy type → EBS snapshot policy
  Then click Next step 🟧

Step 2: Target Resource Type

• Resource type: Select Volume

• Target resource tags:
  Add the tag you used on your EC2 volume, for example:

  • Key: Backup

  • Value: Daily

Only the volumes with this tag will be backed up automatically.

Step 3: Configure Schedule

• Schedule name: Daily-EC2-Backup (or Weekly if preferred)

• Frequency: Every 24 hours (for daily) or Every 7 days (for weekly)

• Start time: Choose off-peak (e.g., 02:00 UTC)

• Retention type: “Count”

• Retain: 7 snapshots (automatically delete older ones)

Enable these options:

• ☑ Copy tags from source

• ☑ Exclude boot volumes (optional — keep unchecked if you want full backups including OS)

Step 4: IAM Role

If this is your first lifecycle policy:

• Choose “Create new role for this policy”
  AWS will auto-generate permissions for DLM to create/delete snapshots.

Step 5: Review and Create

• Review your policy summary (target tag, schedule, retention, IAM role)

• Click Create Policy

Verification

After 24 hours (or at next schedule), go to:
👉 EC2 → Snapshots
You’ll see entries like:

“Created by EC2 Lifecycle Policy: Daily-EC2-Backup”

That confirms your automation works.