Forem: Bhavya Kaushik

Notes on Types of Database: Part 1

Bhavya Kaushik — Tue, 11 Jun 2024 17:14:45 +0000

Single Server Setup: Basics of System Design

Bhavya Kaushik — Mon, 10 Jun 2024 15:52:48 +0000

Designing a system can look very daunting at first.

But it all starts with a small step.

So, while designing a system, we start off with a very simple approach where the system has only one server. Hence, called Single Server Setup.

A single server setup involves running your entire application stack (web server, database, application logic, etc.) on a single physical or virtual machine. It's straightforward, cost-effective, and perfect for startups or small projects where simplicity and budget are key.

Understanding the diagram

Let's say you are a user, who wants to extract some examples of pet animals from www.example.com.
When you access this website through domain name (www.example.com), the web hosting company who is providing Domain Name System (DNS) service to this website will give you an IP address (e.g., 69.89.31.226).
As the IP address is provided, an HTTP (HyperText Transfer Protocol) request is sent to the web server.
The web server will process the request and send the desired output in the form of HTML page or JSON response to your browser. That response is rendered by your web browser and you will be able to see the examples of pet animals.

Like you, many users must be accessing this website. So there are two main sources of traffic that can come to the server:

Web application: This is accessed through a desktop device. Web application combines server-side logic (handling business processes and database communication) with client-side rendering (displaying content in browsers using HTML, CSS, and JavaScript). Together, they create interactive experiences accessible via web browsers.
Mobile application: This is accessed through a mobile device. Mobile apps communicate with the web server through HTTP protocol. As JSON is a very lightweight API response format, it is used to send data from the server.

To conclude, there are many components that we are going to discuss in the system design that will extend this architecture.

.gitignore file IGNORED my .env file

Bhavya Kaushik — Sun, 09 Jun 2024 08:35:09 +0000

I'm learning React.

So while developing a project on React, I was using some Appwrite functionalities to do the backend stuff easily.

I created a .env file and saved all the necessary keys inside it.

I was about to commit the changes when I saw that the .env file was not showing in dark grayish color, instead showing greenish color in VSCode directory structure.

I understood that .gitignore file might not be considering .env file.

When I opened it, I saw that .gitignore does not have ".env" inside it. So, I wrote it. Then refreshed the directory but it was still showing the same result.

After researching, I found out that I need to delete the .env file and then commit it again.

So, this is how I solved this problem:

Copied all the content of .env file in Clipboard and deleted .env file.
Created a new .env file and pasted the copied content inside it.
Updated .gitignore file by adding *.env inside it (Writing .env did not work for me).
Committed the changes in git

git add . git commit -m "Removing the .env file from git" git push origin main