<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Vikas Singh</title>
    <description>The latest articles on DEV Community by Vikas Singh (@vkassingh).</description>
    <link>https://dev.to/vkassingh</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F483273%2Faccbf457-71df-47ea-b2a9-8bcaf6991f63.jpeg</url>
      <title>DEV Community: Vikas Singh</title>
      <link>https://dev.to/vkassingh</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vkassingh"/>
    <language>en</language>
    <item>
      <title>How to create a microsite in next website on gcp server?</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Wed, 26 Nov 2025 06:49:09 +0000</pubDate>
      <link>https://dev.to/vkassingh/how-to-create-a-microsite-in-next-website-on-gcp-server-5fo6</link>
      <guid>https://dev.to/vkassingh/how-to-create-a-microsite-in-next-website-on-gcp-server-5fo6</guid>
      <description>&lt;p&gt;First go to the microsite folder. Upload the zip file of the microsite lets say abc.zip. &lt;/p&gt;

&lt;p&gt;Then bring the abc zip to the current directory. &lt;/p&gt;

&lt;p&gt;Then unzip the folder&lt;/p&gt;

&lt;p&gt;Visit the abc folder directory. Where there is package.json , give the command NPM INSTALL and NPM RUN BUILD.&lt;/p&gt;

&lt;p&gt;Then in same directory give this below command:&lt;br&gt;
ls -l /etc/apache2/sites-enabled&lt;/p&gt;

&lt;p&gt;Find the relevant config files. In my case it was seglko.conf and seglko=ssl.conf . &lt;/p&gt;

&lt;p&gt;Open these conf files and add the routing rules for abc site one by one in both files. &lt;/p&gt;

&lt;p&gt;After that build the file of abc by using command : NPM RUN BUILD&lt;br&gt;
After that restart the server of apache. sudo systemctl restart apache2&lt;/p&gt;

</description>
    </item>
    <item>
      <title>All Linux commands for GCP</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Wed, 26 Nov 2025 05:46:39 +0000</pubDate>
      <link>https://dev.to/vkassingh/all-gcp-commands-3mkg</link>
      <guid>https://dev.to/vkassingh/all-gcp-commands-3mkg</guid>
      <description>&lt;p&gt;change directory: cd directory name&lt;br&gt;
List file and folder: ls&lt;br&gt;
Just Read a file: less filename&lt;br&gt;
Edit a file: nano filename&lt;br&gt;
Save File after edit: ctrl O + enter + ctrl X&lt;/p&gt;

&lt;p&gt;Create a new file: cat&amp;lt;&amp;lt;'EOF'&amp;gt;Filename&lt;br&gt;
filecontent&lt;br&gt;
EOF&lt;/p&gt;

&lt;p&gt;Jump to a new line:Ctrl + _ or Ctrl + shift + -&lt;br&gt;
Remove file: rm filename&lt;br&gt;
Rename file: mv file file1&lt;/p&gt;

&lt;p&gt;Clear previous build: rm -rf .next out build dist&lt;br&gt;
create build: npm run build&lt;br&gt;
Restart server: pm2 restart appname(selgko)&lt;/p&gt;

&lt;p&gt;Create tar backup: tar -cvf filename.tar&lt;br&gt;
Then click on download file in ssh to download file.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>GCP : How to fix Application client side error</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 09 Nov 2025 11:37:25 +0000</pubDate>
      <link>https://dev.to/vkassingh/gcp-how-to-fix-application-client-side-error-5a26</link>
      <guid>https://dev.to/vkassingh/gcp-how-to-fix-application-client-side-error-5a26</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Feb8ulidz9sa1gtr7mypi.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Feb8ulidz9sa1gtr7mypi.jpeg" alt=" " width="800" height="373"&gt;&lt;/a&gt;Go to the directory where there is package.json file. Run these commands&lt;/p&gt;

&lt;p&gt;1.Clear old build.&lt;br&gt;
rm -rf .next out build dist&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;npm run build&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Restart server.&lt;br&gt;
pm2 restart your-app-name(seglko)&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>webdev</category>
      <category>gcp</category>
      <category>linux</category>
    </item>
    <item>
      <title>GCP: Go to specific line of code on ssh / linux</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 09 Nov 2025 11:29:28 +0000</pubDate>
      <link>https://dev.to/vkassingh/gcp-go-to-specific-line-of-code-on-ssh-linux-5ade</link>
      <guid>https://dev.to/vkassingh/gcp-go-to-specific-line-of-code-on-ssh-linux-5ade</guid>
      <description>&lt;p&gt;Jumping to specific line of code while making changes is an important part. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After nano filename.jsx&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Press Ctrl + _ (that's Control + underscore)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Type the line number (e.g., 42)&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Press Enter&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;After less filename.jsx&lt;/strong&gt;&lt;br&gt;
Just type the line number&lt;/p&gt;

</description>
      <category>linux</category>
      <category>googlecloud</category>
      <category>gcp</category>
      <category>devops</category>
    </item>
    <item>
      <title>Ring Based deployment</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 09 Nov 2025 11:19:13 +0000</pubDate>
      <link>https://dev.to/vkassingh/ring-based-deployment-3g3h</link>
      <guid>https://dev.to/vkassingh/ring-based-deployment-3g3h</guid>
      <description>&lt;p&gt;Microsoft used Ring Based deployment to integrate GraphQL to Microsoft teams. So i got curious about Ring based deployment.&lt;/p&gt;

&lt;p&gt;So what we will learn:&lt;br&gt;
&lt;strong&gt;What is Ring Based deployment?&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;What is so special about it?&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;When to use it?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Ring based deployment is like a rehearsel for your software- start small, fix fast and then go big. It is special because it balances speed with safety. Use it when you have a large userbase and when stability and trust matter.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is Ring based deployment?&lt;/strong&gt;&lt;br&gt;
It is a phased rollout strategy where updates are released in RINGS:&lt;br&gt;
First ring: a small group (like internal testers )&lt;br&gt;
Next rings: Gradually larger user groups.&lt;br&gt;
Final ring: Full production roll out.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is special about it?&lt;/strong&gt;&lt;br&gt;
-Catches bugs early, Reduces risk of mass outages, Enables fast rollback if something breaks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When should you use it?&lt;/strong&gt;&lt;br&gt;
-When releaseing critical updates&lt;br&gt;
&lt;strong&gt;-For large scale apps with many users&lt;/strong&gt;&lt;br&gt;
-When uptime and stability are top priorities.&lt;br&gt;
-During feature flag rollouts or A/B testing&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>beginners</category>
      <category>devops</category>
    </item>
    <item>
      <title>How to understand large typescript codebase</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 09 Nov 2025 06:24:06 +0000</pubDate>
      <link>https://dev.to/vkassingh/how-to-understand-large-typescript-codebase-3e9c</link>
      <guid>https://dev.to/vkassingh/how-to-understand-large-typescript-codebase-3e9c</guid>
      <description>&lt;p&gt;-Check package.json, identify dependencies, scripts, and entry points&lt;/p&gt;

&lt;p&gt;-Review tsconfig.json: Learn about compiler settings, path aliases,&lt;br&gt;
and strictness levels.&lt;/p&gt;

&lt;p&gt;-Understand folder structure: like src/ components/ utils/ hooks/&lt;/p&gt;

&lt;p&gt;-Read test cases like tests/ or &lt;em&gt;tests&lt;/em&gt; : these contain unit and &lt;br&gt;
integration tests.&lt;/p&gt;

&lt;p&gt;-Trace the flow.Looks for index.ts file, they often serve as entry points.&lt;/p&gt;

&lt;p&gt;-Follow imports to understand how modules connect.&lt;/p&gt;

&lt;p&gt;-Explore interface and types which are often used.&lt;/p&gt;

&lt;p&gt;-Use UNKNOWN instead of any for safer type handling.&lt;/p&gt;

&lt;p&gt;-Run tests locally to observe how modules interact.&lt;/p&gt;

&lt;p&gt;-Use SOURCEGRAPH or CodeTour to visualize codebases.&lt;/p&gt;

&lt;p&gt;-After understanding , teach the codebase to someone.&lt;/p&gt;

&lt;p&gt;-Draw a sketch or diagram if possible.&lt;/p&gt;

</description>
      <category>typescript</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>How to understand large Golang codebase</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 09 Nov 2025 06:20:37 +0000</pubDate>
      <link>https://dev.to/vkassingh/how-to-understand-large-golang-codebase-2h19</link>
      <guid>https://dev.to/vkassingh/how-to-understand-large-golang-codebase-2h19</guid>
      <description>&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Check go.mod and go.sum. These files contain dependecies and module version&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Understand the folder structure. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Understand common directories like &lt;br&gt;
cmd/: entry points &lt;br&gt;
pkg/: reusable packages&lt;br&gt;
api/ models/ services/&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Trace execution flow: start from main.go and then follow initialisatio&lt;br&gt;
logic, dependency injection if used, routing, &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Read tests like _test.go&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Use tools like sourcegraph to visualize dependencies.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>go</category>
      <category>programming</category>
    </item>
    <item>
      <title>GCP to GitHub CI/CD Setup Steps</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 02 Nov 2025 05:35:25 +0000</pubDate>
      <link>https://dev.to/vkassingh/gcp-to-github-cicd-setup-steps-5nc</link>
      <guid>https://dev.to/vkassingh/gcp-to-github-cicd-setup-steps-5nc</guid>
      <description>&lt;p&gt;Which Should You Use?&lt;br&gt;
GitHub Actions: More flexible if you already use GitHub workflows&lt;br&gt;
Cloud Build: Better integration with GCP, especially for multi-service deployments&lt;/p&gt;

&lt;p&gt;Step 1: Download Code from GCP to Local ,If code is on Compute Engine VM:&lt;/p&gt;

&lt;p&gt;Step 2: Initialize Local Git Repository&lt;/p&gt;

&lt;p&gt;Step 3: Create GitHub Repository&lt;br&gt;
-Create new repo at GitHub.com&lt;br&gt;
-Do not initialize with README&lt;br&gt;
-Copy repository URL&lt;/p&gt;

&lt;p&gt;Step 4: Connect to GitHub&lt;br&gt;
Step 5: Enable GCP APIs&lt;br&gt;
-Enable Cloud Build API&lt;br&gt;
-Enable Cloud Build GitHub App&lt;/p&gt;

&lt;p&gt;Step 6: Connect GitHub to Cloud Build&lt;br&gt;
-Go to Cloud Build → Triggers&lt;br&gt;
Click Connect Repository&lt;br&gt;
Choose GitHub (Cloud Build GitHub App)&lt;br&gt;
Authenticate and select repository&lt;/p&gt;

&lt;p&gt;Step 7: Create Cloud Build Trigger&lt;br&gt;
Step 8: Create cloudbuild.yaml File for app engine, cloud run&lt;br&gt;
and cloud storagae.&lt;/p&gt;

&lt;p&gt;Step 9: Test Automation&lt;br&gt;
Step 10: Verify Deployment&lt;br&gt;
-Check Cloud Build → History&lt;br&gt;
-Wait for green checkmark&lt;br&gt;
-Verify live site updated&lt;/p&gt;

&lt;p&gt;Step 11: Set Permissions&lt;br&gt;
Ensure Cloud Build service account has:&lt;/p&gt;

&lt;p&gt;App Engine: App Engine Admin role&lt;br&gt;
Cloud Run: Cloud Run Admin role&lt;br&gt;
Cloud Storage: Storage Admin role&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Part 2: Steps for a site Development</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 02 Nov 2025 05:18:06 +0000</pubDate>
      <link>https://dev.to/vkassingh/part-2-steps-for-a-site-development-3fdl</link>
      <guid>https://dev.to/vkassingh/part-2-steps-for-a-site-development-3fdl</guid>
      <description>&lt;p&gt;&lt;strong&gt;5. Automated deployment Setup&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;5.1 Create GitHub Actions Workflow&lt;/strong&gt;&lt;br&gt;
Create .github/workflows/deploy.yml:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.2. Alternative: Using Cloud Build&lt;/strong&gt;&lt;br&gt;
Create cloudbuild.yaml in project root:&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;6.GCP Infrastructure setup&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;6.1. Create Storage Bucket&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create bucket&lt;/li&gt;
&lt;li&gt;Configure as website&lt;/li&gt;
&lt;li&gt;Make files publicly accessible&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;6.2. Set Up Load Balancer (For Custom Domain)&lt;/strong&gt;&lt;br&gt;
Create HTTP(S) Load Balancer&lt;br&gt;
Add bucket as backend&lt;br&gt;
Configure SSL certificate&lt;/p&gt;

&lt;p&gt;7.&lt;strong&gt;Connect GitHub with GCP&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;7.1. Create Service Account&lt;/strong&gt;&lt;br&gt;
Go to IAM &amp;amp; Admin &amp;gt; Service Accounts&lt;br&gt;
Create new service account&lt;br&gt;
Add roles: Cloud Build Editor, Storage Admin&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.2. Generate and Add Secrets to GitHub&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create JSON key for service account&lt;/li&gt;
&lt;li&gt;Add to GitHub Secrets:&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;GCP_SA_KEY = Service account JSON&lt;br&gt;
GCP_PROJECT = Project ID&lt;br&gt;
GCP_BUCKET_NAME = Your bucket name&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;8.Domain Configuration (If Using Custom Domain)&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;8.1. DNS Configuration&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;8.2. SSL Certificate&lt;/strong&gt;&lt;br&gt;
Use Google-managed SSL certificate&lt;br&gt;
Update load balancer with domain&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;9.Testing the Pipeline&lt;/strong&gt;&lt;br&gt;
9.1. Make a Test Change&lt;/p&gt;

&lt;p&gt;9.2. Monitor Deployment&lt;br&gt;
Check GitHub Actions tab&lt;br&gt;
Verify Cloud Build logs&lt;br&gt;
Test live site&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;10.Ongoing Development&lt;/strong&gt;&lt;br&gt;
Workflow for Changes:&lt;br&gt;
Make changes locally&lt;br&gt;
Commit and push to GitHub&lt;br&gt;
GitHub Actions automatically:&lt;br&gt;
    it Builds React app&lt;br&gt;
    it Deploys to GCP Storage&lt;br&gt;
Changes go live in 2-5 minutes&lt;/p&gt;

</description>
      <category>google</category>
      <category>devops</category>
      <category>tutorial</category>
      <category>github</category>
    </item>
    <item>
      <title>Part 1: Steps for a site Development</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Sun, 02 Nov 2025 04:52:10 +0000</pubDate>
      <link>https://dev.to/vkassingh/part-1-steps-for-a-site-development-224c</link>
      <guid>https://dev.to/vkassingh/part-1-steps-for-a-site-development-224c</guid>
      <description>&lt;ol&gt;
&lt;li&gt;Develop locally with React.&lt;/li&gt;
&lt;li&gt;Set up GitHub repo.&lt;/li&gt;
&lt;li&gt;Configure GCP Services.&lt;/li&gt;
&lt;li&gt;Test your site is working locally.&lt;/li&gt;
&lt;li&gt;Connect custom domain.&lt;/li&gt;
&lt;li&gt;Set up automation.&lt;/li&gt;
&lt;li&gt;Make changes via GitHub&lt;/li&gt;
&lt;/ol&gt;




&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Develop locally with React.&lt;br&gt;
&lt;code&gt;# Create React app locally first&lt;br&gt;
npx create-react-app my-website&lt;br&gt;
cd my-website&lt;br&gt;
git init&lt;br&gt;
git add .&lt;br&gt;
git commit -m "Initial commit"&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Set up GitHub repo. Connect local repo to github&lt;br&gt;
&lt;code&gt;# Connect local repo to GitHub&lt;br&gt;
git remote add origin https://github.com/yourusername/your-repo-name.git&lt;br&gt;
git branch -M main&lt;br&gt;
git push -u origin main&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Repo structure&lt;br&gt;
&lt;code&gt;my-website/&lt;br&gt;
├── public/&lt;br&gt;
├── src/&lt;br&gt;
├── build/ (generated)&lt;br&gt;
├── .github/workflows/ (CI/CD)&lt;br&gt;
└── package.json&lt;/code&gt;&lt;/p&gt;




&lt;p&gt;3.&lt;strong&gt;Configure GCP Services.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;3.1. &lt;strong&gt;GCP Project Creation&lt;/strong&gt;&lt;br&gt;
Go to Google Cloud Console&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create new project&lt;/li&gt;
&lt;li&gt;Enable billing account&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;3.2. &lt;strong&gt;Required Services&lt;/strong&gt;&lt;br&gt;
Enable these services:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloud Build (CI/CD)&lt;/li&gt;
&lt;li&gt;Cloud Storage (Hosting)&lt;/li&gt;
&lt;li&gt;IAM (Permissions)&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;4.React App configuration.&lt;br&gt;
4.1. Create build script in package.json&lt;br&gt;
&lt;code&gt;{&lt;br&gt;
  "name": "my-website",&lt;br&gt;
  "homepage": "https://your-domain.com",&lt;br&gt;
  "scripts": {&lt;br&gt;
    "build": "react-scripts build",&lt;br&gt;
    "predeploy": "npm run build",&lt;br&gt;
    "deploy": "gh-pages -d build"&lt;br&gt;
  }&lt;br&gt;
}&lt;/code&gt;&lt;/p&gt;

</description>
      <category>devops</category>
      <category>tutorial</category>
      <category>github</category>
      <category>react</category>
    </item>
    <item>
      <title>How to run a nextjs project after cloning from github</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Fri, 31 Oct 2025 07:47:41 +0000</pubDate>
      <link>https://dev.to/vkassingh/how-to-run-a-nextjs-project-after-cloning-from-github-56jj</link>
      <guid>https://dev.to/vkassingh/how-to-run-a-nextjs-project-after-cloning-from-github-56jj</guid>
      <description>&lt;p&gt;Step 1. Run npm install&lt;br&gt;
Step 2. If you get peer dependency error, &lt;br&gt;
Run  npm install --legacy-peer-deps&lt;br&gt;
Step 3. Run npm run build&lt;br&gt;
Step 4. Run npm run dev&lt;/p&gt;

</description>
      <category>github</category>
      <category>nextjs</category>
      <category>npm</category>
    </item>
    <item>
      <title>How to renew ssl certificate on gcp (Apache server)</title>
      <dc:creator>Vikas Singh</dc:creator>
      <pubDate>Fri, 31 Oct 2025 06:52:20 +0000</pubDate>
      <link>https://dev.to/vkassingh/how-to-renew-ssl-certificate-on-gcp-apache-server-2oka</link>
      <guid>https://dev.to/vkassingh/how-to-renew-ssl-certificate-on-gcp-apache-server-2oka</guid>
      <description>&lt;p&gt;Fist open the ssh into your VM.&lt;/p&gt;

&lt;p&gt;Step 1: Check Current Certificate Status for websitename.in&lt;br&gt;
&lt;strong&gt;sudo certbot certificates&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Step 2: Install Certificate for websitename.org&lt;br&gt;
sudo certbot --apache -d websitename.org -d &lt;a href="http://www.websitename.org" rel="noopener noreferrer"&gt;www.websitename.org&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;Step 3: &lt;strong&gt;Type number 2 : Redirect&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
if you are given ooptions to redirect.&lt;/p&gt;

&lt;p&gt;**NOTE: **Replace websitename.org with your site name&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
