DEV Community: Abisha Berci J

Deploying a Job Application Web App Using Nginx

Abisha Berci J — Mon, 31 Aug 2026 14:15:44 +0000

The goal was to take the production build of the application and configure Nginx to serve it as a web server 🚀

Technologies Used:
React
Vite
Node.js
Express.js
Nginx
Ubuntu / WSL

Deployment Process:

Navigate to the project
cd /mnt/d/Doctpro-main/Doctpro-main
Install dependencies
npm install
Create the production build
npm run build
This generated the dist folder containing the optimized production files.
Prepare the Nginx web directory
sudo mkdir -p /var/www/doctpro
Then copied the production files:
sudo cp -r dist/* /var/www/doctpro/
Configure Nginx
The Nginx configuration was edited using:
sudo nano /etc/nginx/sites-available/default
The application was configured to be served from:
/var/www/doctpro
Verify the configuration
sudo nginx -t
The configuration returned:
syntax is ok
test is successful
Start and verify Nginx
sudo service nginx start
Then:
sudo service nginx status
The server showed:
Active: active (running)
Test the deployed application
curl http://localhost
I also verified the HTTP response using:
curl -I http://localhost
The server returned:
HTTP/1.1 200 OK
Server: nginx

Deployment Flow:
React + Vite Application
↓
npm run build
↓
dist/
↓
/var/www/doctpro
↓
Nginx
↓
Web Application

What I Learned

This task helped me understand the practical deployment flow of a web application — from creating a production build to configuring Nginx and verifying that the server is correctly serving the application.

I also learned that Nginx is not just a web server; it can act as an important layer between users and web applications.

Final Result

The Job Application web application was successfully deployed and served using Nginx.

This task gave me hands-on experience with:

Build → Deploy → Configure → Verify → Serve 🚀

Nginx #WebServer #Deployment #React #Vite #NodeJS #ExpressJS #DevOps #WebDevelopment #Linux #ServerDeployment #SoftwareEngineering #LearningByDoing

Monitor Reset Request Logs

Abisha Berci J — Wed, 26 Aug 2026 11:43:55 +0000

Objective:
The objective of this task is to understand and monitor reset request logs generated by a system or application. Monitoring these logs helps identify successful and failed reset requests, detect unusual activities, and support reliable system operation.

Introduction:
System logs are an important part of server and application monitoring. They maintain records of activities and events generated during the operation of a system.
Reset request logs specifically provide information about requests made to reset a particular service, account, session, or other system-related component. Monitoring these logs helps administrators understand the status of requests and identify possible errors or abnormal activities.

What is a Reset Request?
A reset request is a request sent to a system to reset or restore a particular function or component.
Depending on the application, a reset request may relate to:
• User account reset
• Password reset
• Session reset
• Service reset
• Application reset
Each request may generate a corresponding log entry that can be monitored for its status and outcome.

What are Reset Request Logs?
Reset request logs are records created by the system when reset-related requests are received and processed.
A log entry may contain information such as:
• Date and time
• Request type
• User or service identifier
• Request status
• Success or failure information
• Error details
• Processing or response time
These details help in monitoring the health and reliability of the system.

Monitoring Process:
The general process for monitoring reset request logs is:

Access the available application or server log source.
Locate entries related to reset requests.
Check the date and time of each request.
Identify the type of reset request.
Check whether the request was successful or failed.
Review error messages for failed requests.
Look for repeated or unusual requests.
Record important observations.
Report significant issues for further investigation.

Important Log Information to Monitor:

Log Information Purpose

Date and Time Identifies when the request occurred
Request Type Identifies the type of reset requested
User/Service ID Identifies the source of the request
Status Shows whether the request succeeded or failed
Error Message Helps understand failures
Response Time Helps identify performance issues
Repeated Requests Helps identify unusual activity

Example Log Analysis:
A sample reset request log can be represented as:

Time Request Status Observation

10:15 AM Account Reset Success Request processed normally
10:22 AM Password Reset Success No issue observed
10:31 AM Service Reset Failed Error requires investigation
10:45 AM Account Reset Success Request completed successfully From this type of log, successful requests can be confirmed and failed requests can be identified for further investigation.

Why Monitoring is Important:
Monitoring reset request logs is important because it helps to:
• Detect failed requests
• Identify application or server errors
• Monitor request processing
• Detect repeated or unusual requests
• Support troubleshooting
• Maintain system reliability
• Improve operational monitoring
• Maintain a record of system activities

Issues That Can Be Identified:
During log monitoring, administrators may identify issues such as:
• Repeated failed reset requests
• Server timeout errors
• Invalid requests
• Service availability problems
• Unexpected request frequency
• Application errors
• Delayed request processing
These issues can then be investigated by checking related server or application logs.

Best Practices:
The following practices can be followed while monitoring reset request logs:
• Check logs regularly.
• Focus on failed and abnormal requests.
• Record important errors and observations.
• Monitor repeated requests.
• Protect sensitive information contained in logs.
• Avoid modifying or deleting logs without authorization.
• Escalate serious or repeated issues to the responsible team.
• Maintain proper documentation of identified issues.

Expected Outcome:
After completing this task, the administrator should be able to understand the reset request activity, identify successful and failed requests, recognize potential issues from log entries, and report important observations for further investigation.

Conclusion:
Monitoring Reset Request Logs is an important part of system and server monitoring. Logs provide valuable information about reset-related activities and their outcomes. Regular monitoring helps identify failures, unusual activity, and performance-related problems at an early stage. Proper log monitoring and documentation can therefore contribute to better system reliability, troubleshooting, and operational management.

Apple App Store Guidelines

Abisha Berci J — Tue, 25 Aug 2026 13:47:17 +0000

Objective
The objective is to study Apple's App Store Review Guidelines and identify the major requirements that an application should satisfy before being submitted for App Store approval.
The review focuses on application quality, privacy, security, metadata, age rating, legal compliance, user experience, and the App Store submission process overview.
Before submission, developers should verify that the application complies with Apple's current App Review Guidelines and that all required information in App Store Connect is accurate and complete.

Major Areas Reviewed
Safety
The application should provide a safe experience for users. It should not contain prohibited or harmful content and should follow Apple's requirements for user-generated content, communication features and other safety-related functionality.

Performance and Completeness
The application should be fully functional before submission.
Key checks include:
• Test the application on actual devices.
• Fix crashes and major bugs.
• Verify that all important features work correctly.
• Remove placeholder and temporary content.
• Ensure backend services are active when required.
• Provide appropriate review/demo access when login is required.
Apple may reject incomplete applications or applications with obvious technical problems.

Accurate App Store Metadata
All App Store information should accurately represent the application.
The following should be reviewed:
• App name
• Subtitle
• App description
• Keywords
• Screenshots
• App previews
• Category
• Age rating
• Privacy information
Screenshots and previews should demonstrate the actual application experience rather than misleading users.

Privacy and Data Protection
Privacy is a critical requirement for App Store submission.
The application should clearly identify:
• What data is collected.
• Why the data is collected.
• How the data is used.
• Whether data is shared with third parties.
• How long data is retained.
• How users can request deletion of their data.
A privacy policy should be available both through the App Store metadata and in an easily accessible location within the application.

Permissions
The application should request only the permissions that are necessary for its functionality.
Examples include:
• Camera access
• Microphone access
• Location access
• Photo library access
• Contacts access
• Notifications
Permission requests should have a legitimate purpose and should be clearly explained to users.

Age Rating
The correct age rating must be provided through App Store Connect.
The developer must answer Apple's age-rating questionnaire honestly based on the application's content and features.
An application should not receive an inappropriate or misleading age rating.

Intellectual Property and Content Rights
All third-party content used in the application should have appropriate rights or permission.
The development team should verify the licensing of:
• Images
• Videos
• Audio
• Fonts
• Logos
• Trademarks
• Other third-party materials
Business and Payment Requirements
If the application provides paid digital products, subscriptions or other transactions, the applicable Apple payment and business requirements should be reviewed.
All pricing, subscription information and purchase functionality should be clear and functional.

Design and User Experience
The application should provide a professional and consistent user experience.

Important areas include:
• Simple navigation
• Clear buttons and labels
• Consistent layouts
• Proper error messages
• Responsive interfaces
• Accessibility considerations
• Platform-appropriate design
Apple's Human Interface Guidelines can be used as an additional reference for designing applications for Apple platforms.

App Store Connect Requirements
Before submission, the development team should verify:
• Correct application information
• Correct bundle/build selection
• Appropriate category
• Correct age rating
• Privacy policy URL
• App privacy information
• Screenshots and previews
• App description and keywords
• Content rights
• Review information Pre-Submission Checklist
• Application tested on physical Apple devices
• Major bugs and crashes fixed
• All major features verified
• Login and registration tested
• Backend services verified
• App Store metadata reviewed
• Screenshots accurately represent the application
• Age rating completed correctly
• Privacy policy prepared and accessible
• App privacy information completed
• Third-party content and licenses verified
• Payment/subscription functionality tested where applicable
• Required review information prepared
• Final build selected in App Store Connect

Official References:
Apple App Review Guidelines: https://developer.apple.com/app-store/review/guidelines/
App Store Connect Help: https://developer.apple.com/help/app-store-connect/
Human Interface Guidelines: https://developer.apple.com/design/human-interface-guidelines

Deploy a Simple Web Server Using Nginx

Abisha Berci J — Sat, 22 Aug 2026 14:54:11 +0000

Introduction
Nginx (pronounced Engine-X) is a high-performance open-source web server used to host websites and web applications. It is widely used because of its speed, reliability, scalability, and low memory usage. Nginx can also function as a reverse proxy server, load balancer, and HTTP cache.
In this , Ubuntu was accessed through WSL on Windows, Nginx was installed, the web server was started, and its successful deployment was verified using a web browser.

Objective
The objective is to install, configure, and deploy a simple web server using Nginx on an Ubuntu Linux environment running through Windows Subsystem for Linux (WSL). The web server is then verified by accessing it through a web browser.

Procedure:
Step 1: Open Ubuntu through WSL
Open Windows PowerShell and launch Ubuntu using the command:
wsl -d Ubuntu
Ubuntu starts successfully and provides a Linux terminal.
Step 2: Update the Ubuntu Package Repository
Update the package list using the following command:
sudo apt update
This downloads the latest package information from the Ubuntu repositories.
Step 3: Install Nginx
Install the Nginx web server using:
sudo apt install nginx -y
The installation completes successfully.
Step 4: Verify Nginx Installation
Check the installed version:
nginx -v
Output:
nginx version: nginx/1.28.3 (Ubuntu)
This confirms that Nginx has been installed successfully.
Step 5: Start the Nginx Service
Start the web server:
sudo service nginx start
This command starts the Nginx service.
Step 6: Check the Nginx Status
Verify whether the service is running:
sudo service nginx status
Output:
Active: active (running)
This indicates that the Nginx server is running successfully.
Step 7: Verify the Web Server
Open a web browser and enter:
http://localhost
The browser displays the Welcome to nginx! page, confirming that the web server is successfully deployed and accessible.

Result:
The Nginx web server was successfully installed, configured, and deployed on Ubuntu using Windows Subsystem for Linux (WSL). The server was started successfully, its status was verified as active (running), and the default Nginx web page was accessed successfully through http://localhost, confirming the successful deployment of the web server.

Basic Linux Server Identification

Abisha Berci J — Fri, 21 Aug 2026 13:06:01 +0000

1. whoami
Purpose
The whoami command displays the username of the currently logged-in Linux user.
How it works
When the command is executed, Linux checks the current user's login session and prints the username associated with that session.
Why do we use it?
• To identify the current logged-in user.
• To verify which user account is executing commands.
• Useful when switching between multiple users or checking administrator (root) access.
Command
whoami
My Output
abisha_berci
Explanation of Output:
The current logged-in Linux user is abisha_berci.

2. hostname
Purpose
The hostname command displays the name of the Linux computer or server.
How it works
Every Linux system has a unique hostname stored in its configuration. The command reads this value and displays it.
Why do we use it?
• To identify the system or server.
• Useful for managing multiple servers in a network.
• Helps in remote administration and troubleshooting.
Command
hostname
My Output
LAPTOP-R7DDAKUB
Explanation of Output:
The hostname of my Linux system is LAPTOP-R7DDAKUB.

3. uptime
Purpose
The uptime command shows how long the Linux system has been running since the last boot.
How it works
Linux records the system boot time. When uptime is executed, it calculates the difference between the current time and the boot time.
Why do we use it?
• To check system availability.
• To know how long the server has been running without restarting.
• To monitor system workload using load averages.
Command
uptime
My Output
06:30:28 up 1:01, 0 users, load average: 0.02, 0.04, 0.02
Explanation of Output:
• 06:30:28 → Current system time.
• up 1:01 → The Linux system has been running for 1 hour and 1 minute.
• 0 users → No active users are currently logged in.
• load average → Shows the CPU workload over the last 1, 5, and 15 minutes. Lower values indicate the system is not busy.

4. df -h
Purpose
The df (Disk Free) command displays information about the file system and available disk space.
How it works
Linux checks each mounted file system and reports its total size, used space, available space, and usage percentage.
Why do we use it?
• To monitor disk usage.
• To check available storage.
• To prevent storage from becoming full.
• Useful for system maintenance and troubleshooting.
Command
df -h
Meaning of -h
The -h option means human-readable, so the sizes are displayed in MB, GB, or TB instead of bytes.
My Output (Main Filesystem)
/dev/sde 1007G 1.3G 955G 1% /
Explanation of Output:
• Filesystem: /dev/sde – The storage device.
• Size: 1007G – Total disk capacity.
• Used: 1.3G – Disk space currently used.
• Available: 955G – Free disk space.
• Use%: 1% – Percentage of storage currently used.
• Mounted on: / – Root directory of the Linux file system.

I successfully executed and verified the following commands and I have attached the screenshot showing the command outputs for verification.

Linux vs Windows Server: Understanding Server Operating Systems

Abisha Berci J — Thu, 20 Aug 2026 16:25:42 +0000

Introduction

A server needs an operating system to manage hardware, applications, users, security, storage, and network communication. This is called a Server Operating System (Server OS).

Two widely used server operating systems are Linux Server and Windows Server.

What Is a Server OS?

A Server OS provides the platform needed to run applications and services while handling multiple users and requests.

Its main responsibilities include:

Managing CPU, memory, and storage
Handling network connections
Running applications and services
Managing users and permissions
Providing security and monitoring

The basic process is:

User Request → Network → Server → Application → Database → Response

Linux Server

Linux is an open-source operating system widely used for web hosting, cloud computing, containers, and backend applications.

Popular distributions include Ubuntu Server, Debian, Rocky Linux, and Red Hat Enterprise Linux.

Advantages

Open-source and customizable
Generally cost-effective
Strong permission-based security
Excellent support for web and DevOps technologies
Lightweight and flexible

Disadvantages

Can be difficult for beginners
Command-line knowledge is often required
Some commercial applications are mainly designed for Windows

Windows Server

Windows Server is Microsoft's server operating system. It is commonly used in organizations that depend on Microsoft's technology ecosystem.

It supports technologies such as Active Directory, .NET, Microsoft SQL Server, and Azure.

Advantages

User-friendly graphical interface
Strong Microsoft ecosystem integration
Easy centralized management with Active Directory
Suitable for enterprise environments

Disadvantages

Commercial licensing can increase costs
Generally uses more system resources
Less suitable for organizations focused mainly on open-source technologies

Linux vs Windows Server

Feature	Linux Server	Windows Server
License	Mostly open source	Commercial
Cost	Generally lower	Generally higher
Administration	CLI + GUI	GUI + CLI
Customization	Very high	High
Web Hosting	Excellent	Good
Microsoft Technologies	Supported	Excellent
Resource Usage	Often lightweight	Generally higher
Enterprise Management	Strong	Excellent

Which One Should You Choose?

The choice depends on the project's requirements.

Linux is a good choice for web hosting, APIs, cloud platforms, DevOps, containers, and open-source applications.

Windows Server is suitable when an organization depends on Microsoft technologies, Active Directory, or Windows-based applications.

Conclusion

Both Linux and Windows Server are powerful operating systems.

Linux stands out for its flexibility, open-source ecosystem, and widespread use in cloud and DevOps environments, while Windows Server is strong in enterprise management and Microsoft-based environments.

The best choice depends on the application, budget, infrastructure, and technical requirements.

Server Infrastructure Analysis

Abisha Berci J — Thu, 20 Aug 2026 07:30:46 +0000

The purpose is to understand how different server components work together to provide services to users. A server plays an important role in a web-based application because it receives user requests, processes them, communicates with databases and other services, and sends the required response back to the user.
Through this learning task, I gained a basic understanding of how server infrastructure is designed, managed and monitored.

Objective
• To understand the concept of server used in a server.
• To learn about virtual servers and virtualization.
• To understand server architecture and how different components communicate.
• To study the functions of an operating system in a server.
• To understand the relationship between software, virtual servers, operating systems and server architecture.
• To identify a suitable server environment for a web-based application such as O2 Saver.
• To understand the basic requirements of server management.

Understanding Server
A server can be a physical computer or a virtual machine that runs different services and applications. When a user accesses a website or application, the request is sent to the server through the network. The server receives the request, processes it using the required application or backend service, and sends the result back to the user.

For example, if a user performs an action in an application, the request may first reach the web server and then be passed to the backend application. The backend processes the request and, if necessary, communicates with the database. After completing the required operation, the response is sent back to the user.

The basic flow:
User → Internet → Server → Backend Application → Database → Response to User

Virtual Server
A virtual server is a software-based server environment that runs on a physical server using virtualization technology.

The basic structure can be represented as:
Physical Server → Hypervisor → Virtual Server → Operating System → Applications

A hypervisor is software that creates and manages virtual machines and allows multiple virtual environments to share the resources of a physical server.
Some commonly known virtualization technologies are:
• VMware
• KVM
• Microsoft Hyper-V
• VirtualBo

Advantages of Virtual Servers

Cost Efficiency Organizations can use virtual infrastructure without purchasing a separate physical server for every application.
Resource Flexibility CPU, memory and storage resources can be allocated according to application requirements.
Scalability Resources can often be increased when application traffic and workload increase.
Backup and Recovery Depending on the platform, virtual machines can support snapshots and backup mechanisms.
Testing and Development Separate virtual environments can be created for development, testing and production.

Server Architecture
Server architecture describes how different components of a server-based application are arranged and how they communicate with each other.
The communication flow is:
User → Internet → Web Server → Backend Application → Database
The response then travels back:
Database → Backend Application → Web Server → Internet → User
A common web application architecture consists of three main layers.
Presentation Layer
The presentation layer is the part of the application that users interact with.
Examples include:
• Website
• Web browser
• Mobile application
• User interface
Application Layer
The application layer contains the backend logic of the application.
It is responsible for:
• Processing user requests
• Authentication
• API processing
• Business logic
• Data processing
Data Layer
The data layer is responsible for storing and retrieving information.
Examples include:
• MySQL
• PostgreSQL
• MongoDB

Operating System
An Operating System (OS) is system software that manages the computer's hardware and provides an environment for applications to run.
In a server, the operating system is responsible for managing important resources such as:
• CPU
• RAM
• Storage
• Network
• Users
• Processes
• Files
• Security
Common server operating systems include:
• Ubuntu Server
• Debian
• Rocky Linux
• Red Hat Enterprise Linux
• Windows Server
Linux-based operating systems are commonly used in server environments because they provide strong networking, security, automation and administration capabilities.

Functions of an Operating System in a Server
Process Management
The operating system manages all running processes and services.
For example:
• Web server process
• Backend process
• Database process
• Monitoring process
The OS allocates CPU resources to these processes.
Memory Management
The operating system manages RAM and allocates memory to different applications and services.
File Management
The operating system manages:
• Files
• Folders
• Storage
• File permissions
• Directories
Network Management
The OS manages network communication between the server and other systems.
It handles:
• Network interfaces
• Connections
• Ports
• Network services
User Management
The operating system manages user accounts and controls what different users are allowed to access.
Security Management
The OS supports security through:
• User authentication
• Access control
• Permissions
• Firewall configuration
• Security updates
Resource Management
The operating system manages the server's:
• CPU
• RAM
• Storage
• Network resources
Logging and Monitoring
The operating system records important system events and errors through logs. These logs can help administrators identify problems and troubleshoot the server.

Suitable Server Environment
For a web-based application, a Linux-based virtual server or cloud VPS can be considered a practical reference environment.
A possible high-level architecture is:
Users
↓
Internet / HTTPS
↓
Linux Virtual Server / Cloud VPS
↓
Web Server
↓
Backend Application
↓
Database

Server Management Requirements
Important areas include:
Traffic Monitoring
Traffic monitoring helps understand the number of requests and users accessing the application.
Performance Monitoring
Server performance can be monitored using:
• CPU usage
• RAM usage
• Storage usage
• Network usage
• Response time
Log Management
Server and application logs can help identify:
• Errors
• Failed requests
• Service problems
• Abnormal activities
Security
Server security includes:
• Secure user access
• Proper permissions
• Firewall configuration
• HTTPS
• Software updates
• Secure authentication
Backup and Recovery:
Important application and database information should have suitable backup and recovery procedures.
Scalability:
If the number of users or amount of traffic increases, server resources may need to be increased to maintain performance.