Ubuntu Server Environment Setup for CartForge Application

After successfully managing code with GitHub and organizing workflows, the team is ready for the next step—creating a real project environment.

The manager notices that although the code is ready, there is no proper environment to run the project in real conditions.

He calls the Junior DevOps Engineer and explains:
  “Our code is ready, but without a proper server environment, we can’t run or test it effectively.”

He continues:
  “We need a reliable and scalable environment where our application can run like a real-world system.”

The manager suggests the solution:
  “Let’s use AWS and launch an Ubuntu server using EC2.”

1) What is Linux?  2) Why Linux?3) Linux Architecture

4) linux File permission

Go to the aws Management console  And Search EC2

After Search You will see the Ec2 Dashboard

Click on the Launch Instance Button for Creating the Instance

you will see the instance dashboard and info Name and Select Ubuntu OS

Select the Instance type t2 micro (FREE TIER)

Create Key PairClick Create Key Pair

• Name → cartforge-key

• Download .pem file

Scroll down In the Network Setting Allow SSH HTTP and HTTPS

After all done you can launch the instance by click on the launch instance button

After click on the Launch instance  button you will see the instance is running after 2 by 2 checks your instance is ready

After click on the instance checkbox you can see the public IP so copy that public IP

After Click On the copy Open Command Prompt Write Below Command to connect Ec2 Sever

Once Connected , You will see something like

After successfully launching the Ubuntu EC2 server on AWS, the team is excited to start working on it.

But,

The screen is black with only a terminal, and no one knows what to do next

Let Learn Linux Commands

Check Current User

 Check User ID Info

Check Current Location

Check System Info

List File

Show Hidden Files

Go inside folder

Go back

Go to home

Clear Screen

Update Server

After learning basic Linux commands and getting comfortable with the Ubuntu server, the team feels more confident working in the server environment.

The project is not yet running on the server.

manager calls the Junior DevOps Engineer and explains:
“We’ve prepared everything, but we haven’t actually deployed the project.”

He clearly defines the goal:

• Pull the project code from GitHub to the server

• Set up all required dependencies

• Run the application live

He adds:
 “To achieve this, we need to understand the exact Linux commands required for our CartForge project.”

Check Current Location

Go inside a folder

Let me quickly show you some important paths:

/home → user files

/var → logs & data

/etc → configuration files

/opt → optional software

For our project, we will mostly work inside:

/home/ubuntu

Now go to your project

Create Project Directory Structure

Now we will create a clean structure for CartForge.

Create Main Directories

Inside cartforge:

Verify Structure

Create Sample Files

Create a log file

Create script file:

Edit a File

Save file:

• Press CTRL + X

• Press Y

• Press Enter

After successfully setting up the project on the server, the team feels everything is finally in place.

But soon, a new issue arises…

Permission Format

Let me show you something

Output example:

Continue from Previous Lab

Now go to your CartForge project

Check Current Permissions

Check File Ownership

Change Permissions (chmod)

Give full access to owner only

Meaning:

• User → full access

• Group → no access

• Others → no access

Give read + execute to all

Set Permissions for Files

Log file (read + write only)

Script file (executable)

Change Ownership (chown)

Test Access(Try reading config)

Try running script

Great job!

• Launched and connected to an Ubuntu AWS EC2 server using SSH
• Learned Linux commands, server management, and deployment setup
• Implemented secure access, file permissions, and successful application deployment

• Package Management Commands and Process Management Commands in Linux