DEV Community: Achmad Dinofaldi Firmansyah

Deploying a Static Front-End to AWS

Achmad Dinofaldi Firmansyah — Sun, 02 Jul 2023 10:54:24 +0000

Deploying a Vue static front-end to AWS is a straightforward process that allows you to showcase your VueJS application to anyone on the web. In this blog post, we will guide you through the step-by-step process of deploying your VueJS bundle to an AWS S3 bucket and configuring static hosting settings. Let's get started!

Step 1: Creating an S3 Bucket

To begin, navigate to your AWS console and access the S3 service. Once there, click on 'Create Bucket' to initiate the bucket creation process. Choose a unique name for your bucket, ensuring it is relevant to your project.

Step 2: Configuring Bucket Access

To enable public access and allow anyone on the web to view your site, it is necessary to unblock all public access to the bucket. This ensures that the necessary permissions are set correctly. Create the new bucket after configuring the access settings.

Step 3: Uploading Bundled Files

Select your newly created bucket and click on the 'Upload' button. This action will open a file upload dialog. Proceed to drag and drop all the bundled files from the 'dist' directory that was generated by VueJS during the build process. Confirm the upload of all the files.

Step 4: Enabling Static Hosting

In the bucket's properties, scroll down until you find the static hosting settings. Edit the settings and enable hosting for your Vue static front-end. Additionally, set the index document to 'index.html', which serves as the entry point for your application.

Step 5: Configuring Bucket Permissions

Navigate to the bucket's permissions (not properties) and edit the bucket policy to include the provided JSON code. This policy grants the necessary permissions for public read access to objects within the bucket. Make sure to replace 'Bucket-Name' in the code with the actual name of your bucket.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject"
            ],
            "Resource": [
                "arn:aws:s3:::Bucket-Name/*"
            ]
        }
    ]
}

Step 6: Testing the Deployment

After completing all the previous steps, you will find an endpoint URL for your deployed Vue static front-end. To access it, go to your bucket properties and scroll down until you see the endpoint. Click on it to test your deployment and ensure that everything is working correctly.

Deploying a Vue static front-end to AWS using an S3 bucket is a convenient way to make your application accessible to users on the web. By following the steps outlined in this blog post, you can easily configure the necessary settings and policies to ensure your VueJS application is deployed and hosted properly. Enjoy showcasing your Vue project to the world!

Deploying a Flask Application on AWS EC2

Achmad Dinofaldi Firmansyah — Sat, 01 Jul 2023 11:14:42 +0000

In this blog post, we will walk through the process of deploying a Flask application on an AWS EC2 instance. We will cover each step from setting up the environment to configuring Nginx as a reverse proxy. By following these steps, you will be able to successfully deploy your Flask application and make it accessible to the outside world.

Step 1: Update the System

To ensure that our system has the latest package information, run the following command:

sudo apt-get update

This command updates the package lists for upgrades and new installations.

Step 2: Install Python Virtual Environment

To create an isolated Python environment for our project, we need to install the python3-venv package. Execute the following command:

sudo apt-get install python3-venv

Python virtual environments allow us to manage dependencies and isolate our project's environment from the system Python installation.

Step 3: Clone or Create the Project Directory

You have two options here. Either clone an existing project from GitHub using the git clone command, or create a new project directory using the mkdir command followed by the desired project name.

Step 4: Navigate to the Project Directory

Change your current working directory to the project directory using the cd command:

cd project_name

Step 5: Create a Virtual Environment

Now, let's create a virtual environment for our project. Execute the following command:

python3 -m venv venv

This command creates a virtual environment named "venv" inside your project directory.

Step 6: Activate the Virtual Environment

To activate the virtual environment, run the following command:

. venv/bin/activate

Once activated, your command prompt will reflect the virtual environment's name.

Step 7: Install Flask and Dependencies

Next, we need to install Flask and any other project dependencies. Use either of the following commands:

pip install -r requirements.txt

pip install Flask

The first command is used if you have a requirements.txt file listing all the dependencies. The second command installs Flask directly.

Step 8: Run the Flask Application

To ensure everything is working correctly, run the Flask application using the following command:

python app.py

This command starts the Flask development server, allowing you to test your application locally.

Step 9: Install Gunicorn

Gunicorn is a production-ready web server for running Flask applications. Install it using the following command:

pip install gunicorn

Step 10: Run Gunicorn

To run your Flask application with Gunicorn, execute the following command:

gunicorn -b 0.0.0.0:8000 app:app

This command starts Gunicorn, binding it to all available network interfaces on port 8000.

Step 11: Create a Systemd Service File

To run the Flask application as a service, create a systemd service file using the following command:

sudo nano /etc/systemd/system/project_name.service

Step 12: Add Code to the Service File

Inside the service file, add the following code:

[Unit]
Description=Gunicorn instance for a simple app
After=network.target

[Service]
User=ubuntu
Group=www-data
WorkingDirectory=/home/ubuntu/project_name
ExecStart=/home/ubuntu/project_name/venv/bin/gunicorn -b localhost:8000 app:app
Restart=always

[Install]
WantedBy=multi-user.target

This code specifies the service description, user, group, working directory, and the Gunicorn command to start the Flask application.

Step 13: Reload Systemd Daemon

After creating the service file, reload the systemd daemon to make it aware of the new service:

sudo systemctl daemon-reload

Step 14: Start the Service

To start the Flask application service, run the following command:

sudo systemctl start project_name

Step 15: Enable the Service on System Startup

To ensure that the Flask application service starts automatically on system boot, execute the following command:

sudo systemctl enable project_name

Step 16: Test the Application

To verify if the Flask application is running correctly, use the curl command to send a request to the local server:

curl localhost:8000

If everything is set up properly, you should see the response from your Flask application.

Step 17: Install Nginx

To set up Nginx as a reverse proxy, install it using the following command:

sudo apt-get install nginx

Step 18: Start Nginx

To start the Nginx service, run the following command:

sudo systemctl start nginx

Step 19: Enable Nginx on System Startup

To ensure that Nginx starts automatically on system boot, execute the following command:

sudo systemctl enable nginx

Step 20: Configure Nginx

Open the Nginx configuration file using the nano editor:

sudo nano /etc/nginx/sites-available/default

Step 21: Add Upstream and Proxy Pass

Add the following code at the top of the file, below the default comments:

upstream flaskhelloworld {
    server 127.0.0.1:8000;
}

Step 22: Configure Proxy Pass

Inside the location / block, add the following code:

location / {
    proxy_pass http://project_name;
}

This code sets up the reverse proxy to forward requests to the Gunicorn server running on port 8000.

Step 23: Restart Nginx

To apply the Nginx configuration changes, restart the Nginx service:

sudo systemctl restart nginx

Congratulations! You have successfully deployed a Flask application on an AWS EC2 instance using Gunicorn and Nginx as a reverse proxy. Your Flask application is now accessible through the Nginx server, providing a robust and scalable setup for your application.

How to Reset MySQL or MariaDB Root Password on Ubuntu 20.04

Achmad Dinofaldi Firmansyah — Fri, 30 Jun 2023 02:39:25 +0000

Losing or forgetting the root password for your MySQL or MariaDB database server can be a frustrating experience. However, in Ubuntu 20.04, there are specific steps you can follow to reset the root password and regain access to your database. In this article, we will explore the step-by-step process for resetting the root password for both MySQL and MariaDB on Ubuntu 20.04.

MYSQL STEP

Stop the MySQL service by running the following command:

sudo systemctl stop mysql

Open the MySQL service unit file for editing:

sudo systemctl edit mysql

Add the following lines to the editor:

[Service]
ExecStart=
ExecStart=/usr/sbin/mysqld --skip-grant-tables --skip-networking

Save and close the editor. This will create an override for the MySQL service and reload the systemd daemon to apply the changes:

sudo systemctl daemon-reload

Start the MySQL service with the new configuration:

sudo systemctl start mysql

sudo mysql -u root

Inside the MySQL prompt, flush the privileges to ensure the changes take effect:

FLUSH PRIVILEGES;

Set a new password for the root user. Replace 'new_password' with your desired password:

ALTER USER 'root'@'localhost' IDENTIFIED WITH caching_sha2_password BY 'new_password';

Revert the changes made to the MySQL service by running:

sudo systemctl revert mysql

Reload the systemd daemon again:

sudo systemctl daemon-reload

Restart the MySQL service to apply the new password:

sudo systemctl restart mysql

You can now log in to MySQL as the root user using the new password:

mysql -u root -p

MariaDB Step

Stop the MariaDB service:

sudo systemctl stop mariadb

Set an environment variable to start MariaDB with skip-grant-tables and skip-networking options:

sudo systemctl set-environment MYSQLD_OPTS="--skip-grant-tables --skip-networking"

Start the MariaDB service with the new configuration:

sudo systemctl start mariadb

sudo mysql -u root

Inside the MariaDB prompt, flush the privileges:

FLUSH PRIVILEGES;

Set a new password for the root user:

ALTER USER 'root'@'localhost' IDENTIFIED BY 'new_password';

Update the authentication_string column to ensure it's empty:

UPDATE mysql.user SET authentication_string = '' WHERE user = 'root';

Update the plugin column to ensure it's empty:

UPDATE mysql.user SET plugin = '' WHERE user = 'root';

Set the new password using caching_sha2_password authentication plugin:

ALTER USER 'root'@'localhost' IDENTIFIED WITH caching_sha2_password BY 'new_password';

Unset the environment variable to revert the changes:

sudo systemctl unset-environment MYSQLD_OPTS

Restart the MariaDB service:

sudo systemctl restart mariadb

You can now log in to MariaDB as the root user using the new password:

mysql -u root -p

Remember to replace 'new_password' with your desired password in both the MySQL and MariaDB steps.

By following the step-by-step instructions provided in this article, you should be able to successfully reset the root password for both MySQL and MariaDB on Ubuntu 20.04. Remember to choose a strong and secure password to ensure the safety of your database.

How to Deploy Laravel to EC2 AWS

Achmad Dinofaldi Firmansyah — Thu, 29 Jun 2023 01:01:18 +0000

Are you looking to deploy your Laravel application on an EC2 instance in AWS? In this tutorial, we will walk you through the step-by-step process of deploying Laravel to EC2 using Apache as the web server. Let's get started!

Step 1: Install PHP with Apache2

First, we need to install PHP and Apache on our EC2 instance. Connect to your EC2 instance using SSH and run the following commands:

sudo apt-get update
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
sudo apt -y install php7.4
php -v
sudo apt-get install -y php7.4-cli php7.4-json php7.4-common php7.4-mysql php7.4-zip php7.4-gd php7.4-mbstring php7.4-curl php7.4-xml php7.4-bcmath
php -m

This step installs PHP and Apache web server on your EC2 instance. It ensures that you have PHP installed with the necessary extensions required by Laravel.

Step 2: Install Composer

Composer is a dependency management tool for PHP. We need to install Composer to manage the dependencies of our Laravel application. Run the following commands:

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('sha384', 'composer-setup.php') === '756890a4488ce9024fc62c56153228907f1545c228516cbf63f885e036d37e9a59d27d63f46af1d4d07ee0f76181c7d3') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"
sudo mv composer.phar /usr/local/bin/composer

Composer is a dependency management tool for PHP. This step installs Composer on your EC2 instance. Composer will be used to manage the dependencies of your Laravel application.

Step 3: Install Laravel or Clone Laravel from Git

Next, navigate to the /var/www directory and either install Laravel using Composer or clone an existing Laravel project from Git. Here are the commands:

cd /var/www
# Install Laravel using Composer
composer create-project --prefer-dist laravel/laravel your-project-name

# OR

# Clone Laravel project from Git
git clone git@github.com:yourusername/your-repo.git your-project-name

In this step, you navigate to the /var/www directory, which is the default web directory for Apache on Ubuntu. You have two options:

Install Laravel using Composer: This command creates a new Laravel project in the your-project-name directory using the laravel/laravel package.
Clone Laravel project from Git: This command clones an existing Laravel project from a Git repository into the your-project-name directory.

Replace your-project-name with the desired name for your Laravel project.

Step 4: Configure the Environment

After installing Laravel or cloning the project, you need to configure the environment. The .env.example file is copied to .env. You should edit the .env file and set up the appropriate database configuration for your environment.

Copy the .env.example file to .env using the following command:

cp /var/www/your-project-name/.env.example /var/www/your-project-name/.env

Edit the .env file and set up your database configuration according to your environment.
Generate a unique application key by running the following command:

cd /var/www/your-project-name
php artisan key:generate

The php artisan key:generate command generates a unique application key, which is used for encryption and other security-related purposes in Laravel.

Step 5: Database Migration

Laravel provides a migration system to manage database schema changes. The php artisan migrate command runs the database migrations and creates the necessary tables in your database based on the migration files defined in your Laravel project.
Run the database migrations to create the necessary tables in your database:

php artisan migrate

Step 6: Set File and Folder Permissions

To ensure that your Laravel application has the correct file and folder permissions, run the following commands:

sudo chown -R www-data:www-data /var/www/your-project-name
sudo find /var/www/your-project-name -type f -exec chmod 644 {} \;
sudo find /var/www/your-project-name -type d -exec chmod 755 {} \;
cd /var/www/your-project-name
sudo chown -R $USER:www-data .
sudo find . -type f -exec chmod 664 {} \;
sudo find . -type d -exec chmod 775 {} \;

This step ensures that the appropriate file and folder permissions are set for your Laravel project. It ensures that the web server (usually www-data user) has the necessary permissions to access and modify files.
The commands in this step set the ownership and permissions recursively for the Laravel project directory.

Step 7: Configure Apache2

Apache needs to be configured to serve your Laravel application. This step involves creating a new Apache configuration file specific to your project.

Create a new Apache configuration file for your Laravel project:

sudo nano /etc/apache2/sites-available/your-project-name.conf

Paste the following configuration into the file:

<VirtualHost *:80>
    ServerAdmin admin@hwdomain.io
    ServerName laravelapp.hwdomain.io
    DocumentRoot /var/www/your-project-name/public

    <Directory />
        Options FollowSymLinks
        AllowOverride None
    </Directory>
    <Directory /var/www/your-project-name>
        AllowOverride All
    </Directory>

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Replace your-project-name with the actual name of your Laravel project. The ServerName directive should match your desired domain or subdomain.

The configuration file sets the ServerName directive to the desired domain or subdomain for your application. The DocumentRoot points to the public directory of your Laravel project.

Create a symbolic link for the configuration file in the Apache sites-enabled directory:

sudo ln -s /etc/apache2/sites-available/your-project-name.conf /etc/apache2/sites-enabled/your-project-name.conf

Additionally, the configuration enables the necessary overrides and logging for your Laravel application.

Step 8: Restart Apache

Finally, you need to restart the Apache web server for the configuration changes to take effect. This ensures that your Laravel application is now being served by Apache and can be accessed using the specified domain or subdomain.

sudo service apache2 restart

That's it! Your Laravel application is now deployed on an EC2 instance in AWS. You should be able to access it using the specified domain or subdomain.

Remember to configure any additional settings such as DNS records or SSL certificates to make your application accessible over the internet securely.

Congratulations on successfully deploying your Laravel application on EC2 AWS! Happy coding!