DEV Community: Nickson Elauriche Toho

How to run PgAdmin4 with Docker

Nickson Elauriche Toho — Sat, 23 Dec 2023 13:11:29 +0000

Running the docker run command for pgAdmin 4 will start a Docker container with the pgAdmin 4 application. To achieve this, you need to have Docker installed on your system. If you don't have Docker installed, you can download it from the official Docker website: https://www.docker.com/get-started

Here is a basic docker run command to start pgAdmin 4:

docker run --name pgadmin-container -p 0.0.0.0:5050:80 -e PGADMIN_DEFAULT_EMAIL=admin@domain.com -e PGADMIN_DEFAULT_PASSWORD=admin -e PGADMIN_LISTEN_ADDRESS=0.0.0.0 -d dpage/pgadmin4

Let’s break down the command:

-p 0.0.0.0:5050:80: This binds the container's port 80 to all available network interfaces on the host machine (0.0.0.0). This makes pgAdmin 4 accessible from anywhere.
-e PGADMIN_LISTEN_ADDRESS=0.0.0.0: This environment variable sets pgAdmin 4 to listen on all available network interfaces.

---name my_pgadmin4: This option gives a custom name ("my_pgadmin4") to the Docker container. You can choose a different name if you prefer.

-e PGADMIN_DEFAULT_EMAIL=user@example.com: This sets the default email for the initial login.
-e PGADMIN_DEFAULT_PASSWORD=admin: This sets the default password for the initial login.
-d: This runs the container in detached mode, meaning it runs in the background.
dpage/pgadmin4: This is the Docker image for pgAdmin 4. If the image is not already downloaded, Docker will automatically pull it from the Docker Hub.

-After running this command, you should be able to access pgAdmin 4 by opening your web browser and navigating to http://localhost:5050. Use the email and password specified in the docker run command to log in.

Remember to adjust the parameters based on your preferences and requirements. Also, ensure that the chosen port is not already in use on your host machine.

Run MySQL and phpMyAdmin with Docker for Database Management!

Nickson Elauriche Toho — Sat, 23 Dec 2023 12:46:24 +0000

To run MySQL and phpMyAdmin containers with Docker and connect them, you can follow these steps:

Step 1- Install Docker

Make sure you have Docker installed on your machine. You can download and install Docker from the official website: https://www.docker.com/.

Step 2- Create a Docker Network

Create a Docker network to allow the containers to communicate with each other. This step is optional but helps in connecting containers easily.

docker network create mynetwork

Step 3- Run MySQL Container

Run a MySQL container with the desired configuration. Replace <password> with your preferred MySQL password.

docker run -d - name mysql-container - network=mynetwork -e MYSQL_ROOT_PASSWORD=<password> -p 3306:3306 mysql:latest

Step 4- Run phpMyAdmin Container

Run a phpMyAdmin container and link it to the MySQL container. Replace <password> with the MySQL password you set in Step 3.

docker run -d - name phpmyadmin-container - network=mynetwork -e PMA_HOST=mysql-container -e PMA_PORT=3306 -p 8080:80 phpmyadmin/phpmyadmin:latest

Step 5- Access phpMyAdmin

Open your browser and navigate to http://localhost:8080. Log in with the MySQL credentials you provided earlier.

Notes:

Make sure to replace with a secure password of your choice.
You can choose different ports for MySQL and phpMyAdmin if needed.
The — network flag is used to connect containers to the same network, enabling them to communicate with each other using container names.
Ensure that the MySQL container is running before starting the phpMyAdmin container.

By following these steps, you should have a running MySQL container and a phpMyAdmin container connected to it. You can manage your MySQL databases using phpMyAdmin through the web interface.

How to deploy NextJS app on heroku

Nickson Elauriche Toho — Sun, 17 Dec 2023 23:55:04 +0000

To deploy an existing Next.js application to Heroku, you can follow these general steps:

1- Prepare Your Project:

Make sure your Next.js application is set up correctly and is working locally. You should have the necessary project files, including package.json,pages folder, and other dependencies.

2- Create a Git Repository:

If your project isn’t already in a Git repository, initialize one by running:

git init

Create a .gitignore file if you don't have one to exclude unnecessary files from being committed to the repository.

3- Heroku Account:

Make sure you have a Heroku account and have the Heroku CLI installed. You can sign up for Heroku at https://www.heroku.com/ and download the Heroku CLI from https://devcenter.heroku.com/articles/heroku-cli.

4- Log in to Heroku:

Open a terminal and log in to your Heroku account by running:

heroku login

5- heroku login

Create a new Heroku app for your project by running:

heroku create your-app-name

Replace your-app-name with the desired name for your app.

5- Add Build Scripts:

In your package.json file, make sure you have the following scripts defined for building and starting your Next.js app:

"scripts": {
  "build": "next build",
  "start": "next start"
}

7- Configure Environment Variables (if needed):

If your app relies on environment variables, you can set them on Heroku by using the heroku config:set command. For example:

heroku config:set MY_VARIABLE=value

8- Commit and Push to Heroku:

Commit your changes and push your repository to Heroku:

git add .
git commit -m "Initial commit"
git push heroku master

9- Open Your App:

Once the deployment is complete, you can open your app in the browser by running:

heroku open

Your Next.js app should now be deployed to Heroku. Make sure to monitor the deployment process in your terminal for any potential errors. Additionally, remember to set up any necessary database connections or third-party services if your app relies on them, and configure environment variables accordingly on Heroku.

How to deploy Laravel application with Nginx on Ubuntu

Nickson Elauriche Toho — Sun, 17 Dec 2023 13:02:13 +0000

Deploying a Laravel application with Nginx involves setting up the web server to correctly handle the incoming requests and serve your application. Here’s a step-by-step guide to deploying a Laravel application with Nginx:

1- Server setup:

Assuming you have a server with Ubuntu installed, you can start by updating your system:

sudo apt update
sudo apt upgrade

2- Install required software:

Install PHP, Composer, Nginx, and other necessary packages:

sudo apt installcomposer nginx php-fpm php-mysqlphp-json php-mbstring php-xml php-zip php-gd php-curl

3- Confire Nginx:

Create an Nginx server block configuration for your Laravel application. Create a new file in the /etc/nginx/sites-available/ directory (you might need to adjust paths and filenames according to your server setup):

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

Paste the following configuration:

server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/html/your-laravel-project/public;

    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Content-Type-Options "nosniff";

    index index.html index.htm index.php;

    charset utf-8;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    error_page 404 /index.php;

    location ~ \.php$ {
        fastcgi_pass unix:/var/run/php/php8.1-fpm.sock;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        include fastcgi_params;
    }

    location ~ /\.(?!well-known).* {
        deny all;
    }
}

Enable the site configuration:

sudo ln -s /etc/nginx/sites-available/laravel /etc/nginx/sites-enabled/

Test the Nginx configuration:

sudo nginx -t

Restart Nginx:

sudo systemctl restart nginx

4- Deploy Laravel Application:

Upload your Laravel application code to the server. You can use SCP, SFTP, or any other method you prefer.
Set appropriate permissions for the Laravel storage and bootstrap cache directories:

cd /var/www/your_laravel_app
sudo chown -R www-data:www-data storage bootstrap/cache

5- Configure Laravel Environment:

Copy the .env file and configure it with your production settings:

cp .env.example .env
nano .env

Generate an application key:

php artisan key:generate

6- Set Up Database:

If your application uses a database, create the database and update your .envfile with the database credentials.

7- Run Migrations:

Run your application’s migrations to set up the database tables:

Run your application’s migrations to set up the database tables:

php artisan migrate

8- Restart PHP-FPM:

Restart the PHP-FPM service: (Adjust version if necessary)

sudo systemctl restart php7.4-fpm

How to deploy wordpress website with nginx and mysql

Nickson Elauriche Toho — Sun, 17 Dec 2023 10:12:22 +0000

Deploying a WordPress website with Nginx and MySQL involves several steps. Here’s a step-by-step guide to help you set up and deploy your WordPress site. This guide assumes you have a server or hosting environment where you can install and configure Nginx and MySQL. If you’re using a cloud-based hosting provider, the process may vary.

Server Setup

Set up a server or hosting environment (e.g., AWS, DigitalOcean, or a VPS provider) with your preferred Linux distribution (e.g., Ubuntu, CentOS).

Install NGINX

Update your server’s package list: sudo apt update (for Ubuntu) or sudo yum update (for CentOS).
Install Nginx: sudo apt install nginx (for Ubuntu) or sudo yum install nginx (for CentOS).
Start and enable Nginx: sudo systemctl start nginx and sudo systemctl enable nginx.

Install MySQL

Install MySQL Server: sudo apt install mysql-server (for Ubuntu) or sudo yum install mysql-server (for CentOS).
Secure your MySQL installation by running mysql_secure_installation and following the prompts.

Create a MySQL Database and User

Log in to MySQL: mysql -u root -p .
Create a new database for your WordPress site: CREATE DATABASE your_db_name; .
Create a MySQL user and grant privileges to the database:

CREATE USER 'your_username'@'localhost' IDENTIFIED BY 'your_password';
GRANT ALL PRIVILEGES ON your_db_name.* TO 'your_username'@'localhost';
FLUSH PRIVILEGES;

Exit MySQL: EXIT; .

Install PHP-FPM

Install PHP and required extensions: sudo apt install php-fpm php-mysql (for Ubuntu) or sudo yum install php-fpm php-mysql (for CentOS).
Configure PHP-FPM settings if necessary.

WordPress Installation

Download and extract WordPress to your web server root directory:

cd /var/www/html
sudo wget https://wordpress.org/latest.tar.gz
sudo tar -xzvf latest.tar.gz

Set the correct permissions:

sudo chown -R www-data:www-data /var/www/html/wordpress
sudo chmod -R 755 /var/www/html/wordpress

Nginx Configuration

Create an Nginx server block (Virtual Host) configuration for your WordPress site. You can create a new configuration file in /etc/nginx/sites-available/ and symlink it to /etc/nginx/sites-enabled/. Here's a basic configuration:

server {
    listen 80;
    server_name your_domain.com www.your_domain.com;

    root /var/www/html/wordpress;
    index index.php;

    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
    }

    location ~ /\.ht {
        deny all;
    }
}

Test the configuration: sudo nginx -t .
Reload Nginx: sudo systemctl reload nginx .

WordPress Configuration

Open your web browser and access your domain. You will see the WordPress setup wizard.
Follow the instructions to set up your WordPress site, providing the database name, username, and password you created earlier.

WordPress Plugins and Themes

Customize your site by installing themes and plugins as needed.

Secure Your Website

Install an SSL certificate to enable HTTPS for your site.
Implement security best practices, such as using strong passwords, disabling XML-RPC, and regularly updating WordPress and its plugins.

After completing these steps, your WordPress website should be up and running with Nginx and MySQL. Don’t forget to regularly update your WordPress installation, themes, and plugins to keep your website secure and functioning correctly.

How to install GLPI on linux server with NGINX

Nickson Elauriche Toho — Sun, 17 Dec 2023 04:55:53 +0000

To install GLPI on a Linux server with Nginx, you can follow these steps. GLPI is a free and open-source IT asset management and helpdesk system.

1. Prepare your server

Ensure that your Linux server is up-to-date and has the necessary components installed. You’ll need a web server (Nginx), PHP, a database server (usually MySQL or MariaDB), and some additional PHP extensions. You can install these packages using your Linux distribution’s package manager (e.g., apt for Debian/Ubuntu or yum for CentOS/RHEL). For example:

For Debian/Ubuntu

sudo apt update
sudo apt install nginx mysql-server php-fpm php-mysql php-curl php-gd php-ldap php-xml php-mbstring php-zip

For CentOS/RHEL

sudo yum update
sudo yum install nginx mariadb-server php-fpm php-mysql php-curl php-gd php-ldap php-xml php-mbstring php-zip

2. Configure MySQL/MariaDB

Set up a MySQL/MariaDB database and user for GLPI. Replace <db_user>, <db_password>, and <db_name> with your desired values:

mysql -u root -p

CREATE DATABASE <db_name>;
CREATE USER '<db_user>'@'localhost' IDENTIFIED BY '<db_password>';
GRANT ALL PRIVILEGES ON <db_name>.* TO '<db_user>'@'localhost';
FLUSH PRIVILEGES;
EXIT;

3. Download and Extract GLPI

You can download the latest GLPI version from the official website. Upload the downloaded ZIP file to your server and extract it to your web server’s document root directory. For example:

sudo unzip glpi-<version>.zip -d /var/www/html/

4. Set Permissions

Adjust permissions on the GLPI directory to ensure the web server can read and write files as needed:

sudo chown -R www-data:www-data /var/www/html/glpi/

5. Create Nginx Server Block

Create an Nginx server block (virtual host) configuration for GLPI. Replace <your_domain> with your domain name or server IP address:

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

Add the following configuration, making sure to adjust the paths and server_name as needed:

server {
    listen 80;
    server_name <your_domain>;
    root /var/www/html/glpi;

    location / {
        index index.php;
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php7.4-fpm.sock; # Adjust the PHP-FPM socket path
    }

    location ~ /\.ht {
        deny all;
    }
}

6. Enable the Nginx Server Block

Create a symbolic link to your configuration file in the sites-enabled directory:

sudo ln -s /etc/nginx/sites-available/glpi /etc/nginx/sites-enabled/

7. Test Nginx Configuration

Check if your Nginx configuration is correct:

sudo nginx -t

8. Start Nginx

If the configuration test is successful, restart Nginx to apply the changes:

sudo systemctl restart nginx

9. Finish the Installation

Open a web browser and access your GLPI installation using your server’s domain name or IP address. You should see the GLPI installation wizard. Follow the wizard to complete the installation, providing the database credentials and other required information.

10. Secure Your Installation (Optional)

After installation, it’s crucial to secure your GLPI instance. Ensure you change the default administrator password and follow GLPI’s security guidelines.

Your GLPI installation should now be accessible via your web browser and running behind Nginx. Remember to regularly back up your GLPI data and keep the system updated for security purposes.

Configuring Sendy with NGINX: A Step-by-Step Guide

Nickson Elauriche Toho — Sat, 18 Nov 2023 17:20:08 +0000

Sendy is a powerful and cost-effective self-hosted email marketing solution. To optimize its performance and security, integrating it with NGINX, a high-performance web server, is a smart choice. This article will guide you through the process of configuring Sendy with NGINX.

Prerequisites:
Before you begin, make sure you have the following:
Sendy project folder downloaded from SENDY on your server.
NGINX installed on your server.

Step 1: Create NGINX Server Block for Sendy

Navigate to the NGINX sites-available directory. Create a new configuration file for Sendy, for example, sendy.conf.

sudo nano /etc/nginx/sites-available/sendy.conf

Add the following configuration, adjusting the values as needed:

For configure NGINX without SSL config

server {
    listen 80;
    server_name your_sendy_domain.com www.your_sendy_domain.com;

    root /var/www/sendy; # Change this to your Sendy installation directory

    index index.php index.html index.htm;
    autoindex off;

    add_header X-Robots-Tag "noindex, noarchive";
    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Content-Type-Options "nosniff";

    location = /favicon.ico { log_not_found off; access_log off; }
    location = /robots.txt { log_not_found off; access_log off; allow all; }
    location ~ /\.  { deny all; log_not_found off; access_log off; return 404; }

    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        try_files $uri =404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php/php8.1-fpm.sock; # Adjust the PHP version if needed
        fastcgi_index index.php;
        fastcgi_param   SCRIPT_FILENAME $request_filename;
        include fastcgi_params;
    }

    location ~ /\.ht {
        deny all;
    }

    location ~* \.(css|js|gif|jpe?g|png)$ {
        expires max;
        log_not_found off;
    }

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }
    location /l/ {
        rewrite ^/l/([a-zA-Z0-9/]+)$ /l.php?i=$1 last;
    }
    location /t/ {
        rewrite ^/t/([a-zA-Z0-9/]+)$ /t.php?i=$1 last;
    }
    location /w/ {
        rewrite ^/w/([a-zA-Z0-9/]+)$ /w.php?i=$1 last;
    }
    location /unsubscribe/ {
        rewrite ^/unsubscribe/(.*)$ /unsubscribe.php?i=$1 last;
    }
    location /subscribe/ {
        rewrite ^/subscribe/(.*)$ /subscribe.php?i=$1 last;
    }
    location /confirm/ {
        rewrite ^/confirm/(.*)$ /confirm.php?i=$1 last;
    }
    location /new-brand {
        rewrite ^/new-brand/?$ /new-brand.php last;
    }
    location /search-all-brands {
        rewrite ^/search-all-brands/?$ /search-all-brands.php last;
    }
    location /login {
        rewrite ^/login/?$ /login.php last;
    }
    location /settings {
        rewrite ^/settings/?$ /settings.php last;
    }
    location /two-factor {
        if ($arg_i) {
            rewrite ^/two-factor$ /two-factor.php last;
        }
    }
    location = /create {
        if ($arg_i) {
            rewrite ^/create$ /create.php last;
        }
    }
    location = /rules {
        if ($arg_i) {
            rewrite ^/rules$ /rules.php last;
        }
    }
    location = /edit {
       if ($arg_i) {
            rewrite ^/edit$ /edit.php last;
        }
    }
    location = /app {
         if ($arg_i) {
             rewrite ^/app$ /app.php last;
          }
    }
    location = /list {
         if ($arg_i) {
            rewrite ^/list$ /list.php last;
         }
    }
    location = /reports {
        if ($arg_i) {
             rewrite ^/reports$ /reports.php last;
        }
    }
    location = /edit-brand {
        if ($arg_i) {
            rewrite ^/edit-brand$ /edit-brand.php last;
         }
    }
    location = /templates {
        if ($arg_i) {
           rewrite ^/templates$ /templates.php last;
        }
    }
    location = /report {
        if ($arg_i) {
            rewrite ^/report$ /report.php last;
        }
    }
    location = /send-to {
        if ($arg_i) {
            rewrite ^/send-to$ /send-to.php last;
        }
    }
    location = /autoresponders-emails {
        if ($arg_i) {
            rewrite ^/autoresponders-emails$ /autoresponders-emails.php last;
        }
    }
    location = /autoresponders-list {
        if ($arg_i) {
            rewrite ^/autoresponders-list$ /autoresponders-list.php last;
        }
    }
    location = /autoresponders-edit {
        if ($arg_i) {
            rewrite ^/autoresponders-edit$ /autoresponders-edit.php last;
        }
    }
    location = /segments-list {
        if ($arg_i) {
           rewrite ^/segments-list$ /segments-list.php last;
        }
    }
    location = /segment {
        if ($arg_i) {
           rewrite ^/segment$ /segment.php last;
        }
    }
    location = /create-template {
        if ($arg_i) {
           rewrite ^/create-template$ /create-template.php last;
        }
    }
    location = /edit-template{
        if ($arg_i) {
           rewrite ^/edit-template$ /edit-template.php last;
        }
    }
    location = /template-preview {
        if ($arg_i) {
            rewrite ^/template-preview$ /template-preview.php last;
        }
    }
    location = /new-list {
        if ($arg_i) {
            rewrite ^/new-list$ /new-list.php last;
        }
    }
    location = /subscribers {
         if ($arg_i) {
            rewrite ^/subscribers$ /subscribers.php last;
         }
    }
    location = /custom-fields {
         if ($arg_i) {
            rewrite ^/custom-fields$ /custom-fields.php last;
         }
    }
    location = /remove-duplicates {
         if ($arg_i) {
            rewrite ^/remove-duplicates$ /remove-duplicates.php last;
         }
    }
    location = /blacklist-blocked-domains {
         if ($arg_i) {
            rewrite ^/blacklist-blocked-domains$ /blacklist-blocked-domains.php last;
         }
    }
    location = /delete-from-list {
         if ($arg_i) {
            rewrite ^/delete-from-list$ /delete-from-list.php last;
         }
    }
    location = /blacklist-suppression {
         if ($arg_i) {
            rewrite ^/blacklist-suppression$ /blacklist-suppression.php last;
         }
    }
    location = /unsubscribe-from-list {
         if ($arg_i) {
            rewrite ^/unsubscribe-from-list$ /unsubscribe-from-list.php last;
         }
    }
    location = /update-list {
         if ($arg_i) {
            rewrite ^/update-list$ /update-list.php last;
         }
    }
    location ~ ^/housekeeping-(\w+)$ {
         rewrite ^/housekeeping-(\w+)$ /housekeeping-$1.php last;
    }

    access_log /var/log/nginx/sendy_access.log;
    error_log /var/log/nginx/sendy_error.log;
}

For configure NGINX with SSL config

```server {
server_name your_sendy_domain.com www.your_sendy_domain.com;
root /var/www/sendy; # Change this to your Sendy installation directory

index index.php index.html index.htm;
autoindex off;

add_header X-Robots-Tag "noindex, noarchive";
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Content-Type-Options "nosniff";

location = /favicon.ico { log_not_found off; access_log off; }
location = /robots.txt { log_not_found off; access_log off; allow all; }
location ~ /\.  { deny all; log_not_found off; access_log off; return 404; }

location / {
    try_files $uri $uri/ /index.php?$args;
}

location ~ \.php$ {
    try_files $uri =404;
    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    fastcgi_pass unix:/var/run/php/php8.1-fpm.sock; # Adjust the PHP version if needed
    fastcgi_index index.php;
    fastcgi_param   SCRIPT_FILENAME $request_filename;
    include fastcgi_params;
}

location ~ /\.ht {
    deny all;
}

location ~* \.(css|js|gif|jpe?g|png)$ {
    expires max;
    log_not_found off;
}

location / {
    try_files $uri $uri/ /index.php?$query_string;
}
location /l/ {
    rewrite ^/l/([a-zA-Z0-9/]+)$ /l.php?i=$1 last;
}
location /t/ {
    rewrite ^/t/([a-zA-Z0-9/]+)$ /t.php?i=$1 last;
}
location /w/ {
    rewrite ^/w/([a-zA-Z0-9/]+)$ /w.php?i=$1 last;
}
location /unsubscribe/ {
    rewrite ^/unsubscribe/(.*)$ /unsubscribe.php?i=$1 last;
}
location /subscribe/ {
    rewrite ^/subscribe/(.*)$ /subscribe.php?i=$1 last;
}
location /confirm/ {
    rewrite ^/confirm/(.*)$ /confirm.php?i=$1 last;
}
location /new-brand {
    rewrite ^/new-brand/?$ /new-brand.php last;
}
location /search-all-brands {
    rewrite ^/search-all-brands/?$ /search-all-brands.php last;
}
location /login {
    rewrite ^/login/?$ /login.php last;
}
location /settings {
    rewrite ^/settings/?$ /settings.php last;
}
location /two-factor {
    if ($arg_i) {
        rewrite ^/two-factor$ /two-factor.php last;
    }
}
location = /create {
    if ($arg_i) {
        rewrite ^/create$ /create.php last;
    }
}
location = /rules {
    if ($arg_i) {
        rewrite ^/rules$ /rules.php last;
    }
}
location = /edit {
   if ($arg_i) {
        rewrite ^/edit$ /edit.php last;
    }
}
location = /app {
     if ($arg_i) {
         rewrite ^/app$ /app.php last;
      }
}
location = /list {
     if ($arg_i) {
        rewrite ^/list$ /list.php last;
     }
}
location = /reports {
    if ($arg_i) {
         rewrite ^/reports$ /reports.php last;
    }
}
location = /edit-brand {
    if ($arg_i) {
        rewrite ^/edit-brand$ /edit-brand.php last;
     }
}
location = /templates {
    if ($arg_i) {
       rewrite ^/templates$ /templates.php last;
    }
}
location = /report {
    if ($arg_i) {
        rewrite ^/report$ /report.php last;
    }
}
location = /send-to {
    if ($arg_i) {
        rewrite ^/send-to$ /send-to.php last;
    }
}
location = /autoresponders-emails {
    if ($arg_i) {
        rewrite ^/autoresponders-emails$ /autoresponders-emails.php last;
    }
}
location = /autoresponders-list {
    if ($arg_i) {
        rewrite ^/autoresponders-list$ /autoresponders-list.php last;
    }
}
location = /autoresponders-edit {
    if ($arg_i) {
        rewrite ^/autoresponders-edit$ /autoresponders-edit.php last;
    }
}
location = /segments-list {
    if ($arg_i) {
       rewrite ^/segments-list$ /segments-list.php last;
    }
}
location = /segment {
    if ($arg_i) {
       rewrite ^/segment$ /segment.php last;
    }
}
location = /create-template {
    if ($arg_i) {
       rewrite ^/create-template$ /create-template.php last;
    }
}
location = /edit-template{
    if ($arg_i) {
       rewrite ^/edit-template$ /edit-template.php last;
    }
}
location = /template-preview {
    if ($arg_i) {
        rewrite ^/template-preview$ /template-preview.php last;
    }
}
location = /new-list {
    if ($arg_i) {
        rewrite ^/new-list$ /new-list.php last;
    }
}
location = /subscribers {
     if ($arg_i) {
        rewrite ^/subscribers$ /subscribers.php last;
     }
}
location = /custom-fields {
     if ($arg_i) {
        rewrite ^/custom-fields$ /custom-fields.php last;
     }
}
location = /remove-duplicates {
     if ($arg_i) {
        rewrite ^/remove-duplicates$ /remove-duplicates.php last;
     }
}
location = /blacklist-blocked-domains {
     if ($arg_i) {
        rewrite ^/blacklist-blocked-domains$ /blacklist-blocked-domains.php last;
     }
}
location = /delete-from-list {
     if ($arg_i) {
        rewrite ^/delete-from-list$ /delete-from-list.php last;
     }
}
location = /blacklist-suppression {
     if ($arg_i) {
        rewrite ^/blacklist-suppression$ /blacklist-suppression.php last;
     }
}
location = /unsubscribe-from-list {
     if ($arg_i) {
        rewrite ^/unsubscribe-from-list$ /unsubscribe-from-list.php last;
     }
}
location = /update-list {
     if ($arg_i) {
        rewrite ^/update-list$ /update-list.php last;
     }
}
location ~ ^/housekeeping-(\w+)$ {
     rewrite ^/housekeeping-(\w+)$ /housekeeping-$1.php last;
}

access_log /var/log/nginx/sendy_access.log;
error_log /var/log/nginx/sendy_error.log;

listen 443 ssl http2;
ssl_certificate /path/to/your/ssl_certificate.crt;
ssl_certificate_key /path/to/your/ssl_certificate_key.key;

}

server {
if ($host = your_sendy_domain.com) {
return 301 https://$host$request_uri;
}
listen 80;
server_name your_sendy_domain.com;
return 404;
}```

Save the file and create a symbolic link to it in the sites-enabled directory:

sudo ln -s /etc/nginx/sites-available/sendy.conf /etc/nginx/sites-enabled/

Test the NGINX configuration:

sudo nginx -t

If the test is successful, reload NGINX:

sudo service nginx reload

Step 2: Update Sendy Configuration

Edit the Sendy settings file:

nano /var/www/sendy/includes/config.php

Update the following lines with your server information:

```define('APP_PATH', 'https://your_sendy_installation_url');

/* MySQL database connection credentials (place values between the apostrophes) */
$dbHost = ''; //MySQL Hostname
$dbUser = ''; //MySQL Username
$dbPass = ''; //MySQL Password
$dbName = ''; //MySQL Database Name

/* Set this if you use a non standard MySQL port. */
$dbPort = 3306; ```

Save the changes and exit.

Step 3: Test the Configuration

Open your web browser and navigate to your Sendy domain. If everything is configured correctly, you should see the Sendy login page.