Forem: ilhamsabir

💬 Waaku: Manage Multiple WhatsApp Sessions with One Dashboard

ilhamsabir — Mon, 06 Oct 2025 02:57:49 +0000

Ever tried running more than one WhatsApp Web session… and realized you can’t? 😩

For developers building chatbots, automation tools, or customer service dashboards, that’s a huge limitation.

So I built Waaku 🚀 —

an open-source multi-session WhatsApp manager with:

✅ Real-time dashboard

✅ Secure API (REST + WebSocket)

✅ Docker support out of the box

Fork it, run it, and instantly manage multiple WhatsApp accounts like a pro.

🔥 Why You’ll Love Waaku

Multi-session → no more juggling one account at a time
Real-time dashboard → scan QR, see status, monitor errors instantly
Swagger API → send messages, validate numbers, restart sessions via REST
Secure Auth → SHA-512 API keys (raw key never touches the server)
Dockerized → works anywhere in minutes

It’s basically WhatsApp Web on steroids 💪

🛠️ Tech Stack at a Glance

Layer	Tech
Frontend	Vue 3 + Vite + Tailwind + Socket.IO
Backend	Node.js + Express + whatsapp-web.js
Real-time	Socket.IO
Auth	UUIDv4 + SHA-512 API keys
Docs	Swagger (`/api-docs`)
Deploy	Docker + docker-compose

🚀 Quick Start

# Clone the repo
git clone https://github.com/ilhamsabir/waaku_project.git
cd waaku_project

# Copy env file and configure
cp .env.example .env

# Build & run with Docker
docker compose up --build -d

⚡ Example: Validate a Number

curl -X POST http://localhost:4300/api/sessions/session1/validate \
  -H "Content-Type: application/json" \
  -H "X-API-Key: <your-raw-uuidv4>" \
  -d '{"to": "6281234567890"}'

Boom 💥 — instant validation.

🔎 Behind the Scenes

Waaku keeps your dashboard in sync without polling:

QR code generated? → pushed instantly via Socket.IO
Session ready? → dashboard updates in real-time
Error? → you’ll see it right away

Built on whatsapp-web.js but wrapped in a much more developer-friendly flow.

🗺️ Roadmap

Some ideas in the pipeline:

✅ Automated testing (unit + integration)
✅ Redis for distributed rate limiting
✅ Notifications (Slack/Telegram when a session drops)
✅ Plugin-ready UI

Got suggestions? Open an issue or PR 🙌

🚀 Final Thoughts

WhatsApp is powerful, but its limits slow us down.
With Waaku, you finally get a multi-session, real-time, Dockerized WhatsApp manager that’s flexible enough for side projects, startups, or production systems.

I’m excited to see what you build with it. Fork the repo today 👇

👉 https://github.com/ilhamsabir/waaku_project

Send Message BOT Telegram NodeJs

ilhamsabir — Wed, 13 Mar 2024 04:08:38 +0000

Send Message BOT Telegram NodeJs

Intruduction

Create telegram bot to send message from NODEJS Apps.

Create BOT Telegram

Goto BotFather
Open it from mobile device or web.telegram.org
type

  \newbot

Follow instruction
When completed youll get API Token, copy it to somewhere saved.

Test BOT

Open Postman/Insomnia or anything like that.
Create GET request sample.

    # HTTP request format
    # https://api.telegram.org/bot<token>/METHOD_NAME

    # our first method /getMe
    https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe

Now you can see your user data

Building NodeJS

Init nodejs app

    # configure as needed
    npm init;

    # install dependencies
    npm i express axios body-parser --save;

    # create main file
    touch index.js;

Create index.js

    // Dependencies
    const express = require('express');
    const app = express();
    const axios = require('axios');
    const bodyParser = require('body-parser');
    const port = 80;
    const url = 'https://api.telegram.org/bot';
    const apiToken = '{api-token-given-by-BotFather}';
    // Configurations
    app.use(bodyParser.json());
    // Endpoints
    app.post('/', (req, res) => {
        // console.log(req.body);
        const chatId = req.body.message.chat.id;
        const sentMessage = req.body.message.text;
        // Regex for hello
        if (sentMessage.match(/hello/gi)) {
            axios.post(`${url}${apiToken}/sendMessage`,
                {
                        chat_id: chatId,
                        text: 'hello back 👋'
                })
                .then((response) => {
                        res.status(200).send(response);
                }).catch((error) => {
                        res.send(error);
                });
        } else {
            // if no hello present, just respond with 200
            res.status(200).send({});
        }
    });
    // Listening
    app.listen(port, () => {
        console.log(`Listening on port ${port}`);
    });

Try access route and it will send notif to your telegram

Reference

Create bot telegram

Dockerize NodeJS

ilhamsabir — Wed, 13 Mar 2024 04:04:27 +0000

How to dockerize nodejs app

Step 1: Install Docker

To begin with, it’s required to have Docker on your computer. You can download Docker Desktop from the below link and once it’s downloaded and installed successfully, launch the Docker Desktop on your computer.

Step 2: Create a containerised application

The next step is to containerise your application using Docker. To containerise your application you need to have a Dockerfile that is written in YAML. Let’s create a Dockerfile using node as the base image.

I created a simple Node.js application and my working directory contains the below files.

hello-world
  - app.js
  - package-lock.json
  - package.json

Then I need to create a Dockerfile inside this directory.

FROM node:10.23-alpine

WORKDIR /usr/src/app

COPY package*.json ./

RUN npm install

COPY . .

EXPOSE 8080

CMD ["node", "app.js"]

After you add the Dockerfile, you can create the docker image for your application. Use the below command for that [make sure you’re in the same directory where your Dockerfile resides].

$ docker build . -t <image-name>
Eg:
$ docker build . -t node-app

Step 3: Push your image to a Container Registry

For this demonstration, I am using Docker Hub as the container registry. But you can choose any other container registry as you prefer.

To start with, go to Docker Hub and create a new account. Then sign in and go to Repositories > Create Repository. Add a Name to your repository [you can also add a description to your repository but it’s optional] and you can choose whether it keeps as a public or a private repository [if you’re using a free plan, you can create only one private repository in your account].

Then you need to log in to your Docker Hub account using your terminal. For that, use the below command and provide your credentials where necessary.

$ docker login <container-registry-name> -u <username> -p <password>

This is the general command which you can use to log into your account. But the drawback of using this command is, you have to enter your password in plain text. Therefore, use one of the following commands so that your password will not be visible even on the terminal.

$ docker login <container-registry-name>
// then hit enter & provide your username and password
- OR -
$ docker login <container-registry-name> -u <username>
// then hit enter and provide your password

Since I’m using Docker Hub as the container registry you can use docker login command on the terminal and provide credentials without specifying the container registry name.

Eg: type docker login and hit enter
$ docker login
Username: <username>
Password: <password>
// provide credentials and hit enter

After you get Login Succeeded as the output on your terminal, you can start docker tagging and docker pushing.

docker tag command help you to give a tag to your docker image while docker push command pushes it into the Docker Hub. Let’s see how to use these commands on the terminal.

$ docker tag SOURCE_IMAGE[:TAG] TARGET_IMAGE[:TAG]
SOURCE_IMAGE[:TAG] - you can keep this as your local image
TARGET_IMAGE[:TAG] - <username>/<image-name>:<tag>
Eg:
$ docker tag node-app mikej/node-app:v1.0

The above command will tag your image and next you can use the docker push command as below and it will push your image or a repository to a registry.

$ docker push --help
Usage: docker push [OPTIONS] NAME[:TAG]
Push an image or a repository to a registry
Options:
--disable-content-trust   Skip image signing (default true)
Eg:
$ docker push mikej/node-app:v1.0

Install Mongodb on PHP Mac OS Montery (M1)

ilhamsabir — Wed, 13 Mar 2024 03:43:40 +0000

Install Mongodb on PHP Mac OS Montery (M1)

Install the PHP MongoDB Extension before installing the PHP Library for MongoDB. It is worth noting, that full MongoDB driver experience is provided by installing both the low-level extension (which integrates with our C driver) and high-level library, which is written in PHP.

But to make windows terminal look beauty we need to add a theme, so lets start.

Prerequisites

Install PECL
```
brew install pecl
```
Install pcre2
```
brew install pcre2
```

Tutorial

Install mongodb extension
```
pecl install mongodb
```
Enabled extension on PHP.ini
```
extension=mongodb.so
```
To verify installation.
```
php -i | grep mongodb
```

You shoul see output.

$ php -i|grep mongo
mongodb
libmongoc bundled version => 1.17.2
libmongoc SSL => enabled
libmongoc SSL library => Secure Transport
libmongoc crypto => enabled
libmongoc crypto library => Common Crypto
libmongoc crypto system profile => disabled
libmongoc SASL => enabled
libmongoc ICU => disabled
libmongoc compression => enabled
libmongoc compression snappy => enabled
libmongoc compression zlib => enabled
libmongoc compression zstd => enabled
libmongocrypt bundled version => 1.0.4
libmongocrypt crypto => enabled
libmongocrypt crypto library => Common Crypto

Error

When error appear.

Copy pcre2 to your php dir

  cp /opt/homebrew/Cellar/pcre2/10.xxxx/include/pcre2.h /opt/homebrew/Cellar/php@7.xxx/7.xxx/include/php/ext/pcre/pcre2.h

notes Change pcre2 version & php version with your local machine version.

Run
```
sudo pecl install mongodb
```
It should fix your error.

Source

Install MYSQL on Ubuntu server 18.04

ilhamsabir — Tue, 18 Jan 2022 02:49:30 +0000

Install MYSQL on Ubuntu server 18.04

MySQL is an open-source database management system, commonly installed as part of the popular LAMP (Linux, Apache, MySQL, PHP/Python/Perl) stack. It uses a relational database and SQL (Structured Query Language) to manage its data.

The short version of the installation is simple: update your package index, install the mysql-server package, and then run the included security script.

Prerequisites

To follow this tutorial you will need:
- One Ubuntu 18.04 server set up by following this initial server setup guide, including a non-root user with sudo privileges and a firewall.

Installing MySQL

To install it, update the package index on your server with apt:

sudo apt update

Then install the default package:

sudo apt install mysql-server

This will install MySQL, but will not prompt you to set a password or make any other configuration changes. Because this leaves your installation of MySQL insecure, we will address this next.

Configuring MySQL

For fresh installations, you’ll want to run the included security script. This changes some of the less secure default options for things like remote root logins and sample users. On older versions of MySQL, you needed to initialize the data directory manually as well, but this is done automatically now.

Run the security script:

sudo mysql_secure_installation

This will take you through a series of prompts where you can make some changes to your MySQL installation’s security options. The first prompt will ask whether you’d like to set up the Validate Password Plugin, which can be used to test the strength of your MySQL password. Regardless of your choice, the next prompt will be to set a password for the MySQL root user. Enter and then confirm a secure password of your choice.

Note that even though you’ve set a password for the root MySQL user, this user is not configured to authenticate with a password when connecting to the MySQL shell. If you’d like, you can adjust this setting by following Step 3.

Regardless of how you installed it, MySQL should have started running automatically. To test this, check its status.

systemctl status mysql.service

you’ll see output similar to the following:

● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en
   Active: active (running) since Wed 2018-04-23 21:21:25 UTC; 30min ago
 Main PID: 3754 (mysqld)
    Tasks: 28
   Memory: 142.3M
      CPU: 1.994s
   CGroup: /system.slice/mysql.service
           └─3754 /usr/sbin/mysqld

How To Allow Remote Access to MySQL

One of the more common problems that users run into when trying to set up a remote MySQL database is that their MySQL instance is only configured to listen for local connections. This is MySQL’s default setting, but it won’t work for a remote database setup since MySQL must be able to listen for an external IP address where the server can be reached. To enable this, open up your mysqld.cnf file:

sudo nano /etc/mysql/mysql.conf.d/mysqld.cnf

Navigate to the line that begins with the bind-address directive. It will look like this:

. . .
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            = 127.0.0.1
. . .

By default, this value is set to 127.0.0.1, meaning that the server will only look for local connections. You will need to change this directive to reference an external IP address. For the purposes of troubleshooting, you could set this directive to a wildcard IP address, either *, ::, or 0.0.0.0:

. . .
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            = 0.0.0.0
. . .

Then restart the MySQL service to put the changes you made to mysqld.cnf into effect:

sudo systemctl restart mysql

If you have an existing MySQL user account which you plan to use to connect to the database from your remote host, you’ll need to reconfigure that account to connect from the remote server instead of localhost. To do so, open up the MySQL client as your root MySQL user or with another privileged user account:

sudo mysql

Create user for remotely server:

CREATE USER 'user_name'@'%' IDENTIFIED BY 'password';

GRANT ALL PRIVILEGES ON *.* TO 'user_name'@'%' WITH GRANT OPTION;

FLUSH PRIVILEGES;

exit

Now user for accessing remotely db server is on.

Allow UFW

Lastly, assuming you’ve configured a firewall on your database server, you will also need to open port 3306 — MySQL’s default port — to allow traffic to MySQL.
If you only plan to access the database server from one specific machine, you can grant that machine exclusive permission to connect to the database remotely with the following command. Make sure to replace remote_IP_address with the actual IP address of the machine you plan to connect with:

sudo ufw allow from remote_IP_address to any port 3306

sudo ufw allow 3306

And now access your mysql server

mysql -u user -h database_server_ip -p

Or use apps like HeidiSQL, SequelPro, Navicat , Workbeanch , etc.

Setup NGINX For Load Balancer

ilhamsabir — Thu, 06 Jan 2022 03:24:15 +0000

Setup Nginx Load Balancing

Loadbalancing is a useful mechanism to distribute incoming traffic around several capable Virtual Private servers.By apportioning the processing mechanism to several machines, redundancy is provided to the application -- ensuring fault tolerance and heightened stability. The Round Robin algorithm for load balancing sends visitors to one of a set of IPs. At its most basic level Round Robin, which is fairly easy to implement, distributes server load without implementing considering more nuanced factors like server response time and the visitors’ geographic region.

Setup

The steps in this tutorial require the user to have root privileges on your VPS. You can see how to set that up in the Users Tutorial.

Prior to setting up nginx loadbalancing, you should have nginx installed on your VPS. You can install it quickly with apt-get:

sudo apt-get install nginx

Upstream Module

In order to set up a round robin load balancer, we will need to use the nginx upstream module. We will incorporate the configuration into the nginx settings.

Go ahead and open up your website’s configuration (in my examples I will just work off of the generic default virtual host):

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

We need to add the load balancing configuration to the file.

First we need to include the upstream module which looks like this:

# Define which servers to include in the load balancing scheme.
# It's best to use the servers' private IPs for better performance and security.
# You can find the private IPs at your UpCloud control panel Network section.
http {
   upstream server {
        server domain-1.com;
        server domain-2.com;
        server domain-3.com;
   }

   # This server accepts all traffic to port 80 and passes it to the upstream.
   # Notice that the upstream name and the proxy_pass need to match.
   server {
        # Add this if use HTTPS
        listen              443 ssl default_server;
        listen              [::]:443 ssl default_server;
        server_name  localhost;
        ssl_certificate /etc/ssl/certs/nginx-selfsigned.crt;
        ssl_certificate_key /etc/ssl/private/nginx-selfsigned.key;

        location / {
            proxy_pass http://server;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "Upgrade";
            proxy_set_header Host            $host;
            proxy_set_header X-Real-IP       $proxy_protocol_addr;
            proxy_set_header X-Forwarded-For $proxy_protocol_addr;
            # Very important, controls proxied websocket connection timeout
            proxy_read_timeout 600s;
        }
   }
}

Restart nginx:

sudo service nginx restart

Load balancing methods

Load balancing with nginx uses a round-robin algorithm by default if no other method is defined, like in the first example above. With round-robin scheme each server is selected in turns according to the order you set them in the load-balancer.conf file. This balances the number of requests equally for short operations.

Least Connection

Least connections based load balancing is another straightforward method. As the name suggests, this method directs the requests to the server with the least active connections at that time. It works more fairly than round-robin would with applications where requests might sometimes take longer to complete.

To enable least connections balancing method, add the parameter least_conn to your upstream section as shown in the example below.

upstream backend {
   least_conn;
   server 10.1.0.101;
   server 10.1.0.102;
   server 10.1.0.103;
}

Weight

One way to begin to allocate users to servers with more precision is to allocate specific weight to certain machines. Nginx allows us to assign a number specifying the proportion of traffic that should be directed to each server.

A load balanced setup that included server weight could look like this:

upstream backend  {
  server backend1.example.com weight=1;
  server backend2.example.com weight=2;
  server backend3.example.com weight=4;
}

Hash

IP hash allows servers to respond to clients according to their IP address, sending visitors back to the same VPS each time they visit (unless that server is down). If a server is known to be inactive, it should be marked as down. All IPs that were supposed to routed to the down server are then directed to an alternate one.

The configuration below provides an example:

upstream backend {
  ip_hash;
  server   backend1.example.com;
  server   backend2.example.com;
  server   backend3.example.com  down;
 }

Max Fails

According to the default round robin settings, nginx will continue to send data to the virtual private servers, even if the servers are not responding. Max fails can automatically prevent this by rendering unresponsive servers inoperative for a set amount of time.

There are two factors associated with the max fails: max_fails and fall_timeout. Max fails refers to the maximum number of failed attempts to connect to a server should occur before it is considered inactive. Fall_timeout specifies the length of that the server is considered inoperative. Once the time expires, new attempts to reach the server will start up again. The default timeout value is 10 seconds.

A sample configuration might look like this:

upstream backend  {
  server backend1.example.com max_fails=3  fail_timeout=15s;
  server backend2.example.com weight=2;
  server backend3.example.com weight=4;
 }

Create Simple EC2 Instance Using Terraform AWS

ilhamsabir — Mon, 08 Nov 2021 03:44:46 +0000

Terraform is an open-source infrastructure as code software tool that enables you to safely and predictably create, change, and improve infrastructure.

Prerequisites

To follow this tutorial you will need:
- The Terraform CLI (0.14.9+) installed.
- The AWS CLI installed.
- An AWS account.
- Your AWS credentials. You can create a new Access Key on this page.
- Create "Key Pair" on your AWS instances and save .pem file

Configure AWS Account

The AWS CLI supports using any of multiple named profiles that are stored in the config and credentials files. You can configure additional profiles by using aws configure with the --profile option, or by adding entries to the config and credentials files.

The following example shows a credentials file with two profiles. The first [default] is used when you run a AWS CLI command with no profile. The second is used when you run a AWS CLI command with the --profile user1 parameter.

    ~/.aws/credentials (Linux & Mac) or %USERPROFILE%\.aws\credentials (Windows)

Edit your aws credentials

[default]
aws_access_key_id=AKIAIOSFODNN7EXAMPLE
aws_secret_access_key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

[user1]
aws_access_key_id=AKIAI44QH8DHBEXAMPLE
aws_secret_access_key=je7MtGbClwBF/2Zp9Utk/h3yCo8nvbEXAMPLEKEY

Edit your aws config

[default]
region=us-west-2
output=json

[profile user1]
region=us-east-1
output=text

Initialize Terraform

Create directory for your configuration.

mkdir learn-terraform-aws-instance

Change into directory.

cd learn-terraform-aws-instance

Create terraform file.

touch main.tf

Open main.tf in your text editor, paste in the configuration below, and save the file.

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 3.27"
    }
  }
}

### Provider
provider "aws" {
  profile = "your_aws_config_profile"
  region  =  "ap-southeast-1"
}

### ECS Security Group - ALB -> ECS, SSH -> ECS
resource "aws_security_group" "ecs_service_sg" {
  name        = "ecs_service_sg"
  description = "Allow HTTP, HTTPS and SSH traffic"

  ingress {
    description = "SSH"
    from_port   = 22
    to_port     = 22
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }

  ingress {
    description = "HTTPS"
    from_port   = 443
    to_port     = 443
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }

  ingress {
    description = "HTTP"
    from_port   = 80
    to_port     = 80
    protocol    = "tcp"
    cidr_blocks = ["0.0.0.0/0"]
  }

  egress {
    from_port   = 0
    to_port     = 0
    protocol    = "-1"
    cidr_blocks = ["0.0.0.0/0"]
  }

  tags = {
    Name = "global-ecs-service-sg-tf"
  }
}

### EC Instance
resource "aws_instance" "sample_instance_name" {
  ### Ami for ubuntu 18.x.x
  ami           = "ami-0907c2c44ea451f84"
  instance_type = "t2.micro"
  key_name      = "your_key_pair_name"

  ### Get From aws_security_group
  vpc_security_group_ids = [
    aws_security_group.ecs_service_sg.id
  ]

  tags = {
    Name = "SampleTagYourInstanceName"
  }
}

Initialize your terraform project.

terraform init

Deploy terraform

terraform apply

Destroy terraform

terraform destroy

Change Terraform infrastructure

Change your configuration on your .tf file & saved it.
Reinit terraform
```
terraform init
```
Re apply
```
terraform apply
```
Your prev infrastructure will destroy , and terraform create the new one.
Now Yout instance have been created, check your aws instance dashboard
To access your instance use SSH , from your key pair

Access Via SSH

Linux & MacOS usage

Open an SSH client.
Locate your private key file. The key used to launch this instance is your_key.pem
Run this command, if necessary, to ensure your key is not publicly viewable.
```
chmod 400 your_key.pem
```

Connect to your instance using its Public DNS:

your_public_ip4_dns or public_ip4_ip_address

Sample access.

    ssh -i "your_key.pem" ubuntu@your_public_ip4_dns

Windows usage

Download Termius
Create new host
Paste your_public_ip4_dns to "address"
Load your_key.pem
And Connect.

Notes

Source:

4 Mistakes I Made as a Programmer, but I Had To Become a CTO To See Them

ilhamsabir — Fri, 11 Jun 2021 03:00:18 +0000

Original POST
https://betterprogramming.pub/4-mistakes-i-made-as-a-programmer-but-i-had-to-become-a-cto-to-see-them-19a41ba70411

Windows 10 Nginx + PHP

ilhamsabir — Wed, 24 Mar 2021 00:51:16 +0000

NGINX can interface with PHP on Windows via a FastCGI daemon, which ships with PHP: php-cgi.exe. You need to run php-cgi.exe -b 127.0.0.1: and use fastcgi_pass 127.0.0.1:; in the NGINX configuration file. After being launched, php-cgi.exe will keep listening for connections in a command prompt window. To hide that window, use the tiny utility RunHiddenConsole

First

Download nginx, choose stable version.
Download PHP, choose non stable version.

Second

Extract nginx to "C:\nginx"
Extract php to "C:\php"
Create folder "www" in your "C" system , "C:\www"

Third

Edit your nginx.conf at "C:\nginx\conf\nginx.conf"
Change root
```
    root c:/www;
```
Save nginx.conf
Open yout php folder, find php-ini-development

Edit your php-ini-development, like down below.

    extension_dir = "ext" 
    enable_dl = On 
    cgi.force_redirect = 1 
    fastcgi.impersonate = 1 
    cgi.rfc2616_headers = 1 
    extension=php_gd2.dll 
    extension=php_mbstring.dll 
    extension=php_exif.dll 
    extension=php_mysql.dll 
    extension=php_mysqli.dll 
    extension=php_pdo_mysql.dll 
    date.timezone = "Asia/Jakarta"

Save it.
Open your nginx.conf again

Uncoment on php configuration and change to this

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9999
    location ~ \.php$ {
        fastcgi_pass   127.0.0.1:9999;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
        include        fastcgi_params;
    }

Save nginx.conf again.

Fourth

Set Php path
Open your environment variable
- Open "edit the system environment variables"
- Click, "Environtment variables ..."
- Edit "path" on "Sytem ariables"
- Add new path "C:\php"

Create nginx start, stop & restart .bat

Download RunHiddenConsole first, and move RunHiddenConsole.exe to "C:\".

Create file "nginx-start.bat", edit file with down below, make your php-cgi.exe port same as in nginx.conf

    @ECHO OFF

    ECHO Starting PHP FastCGI...
    C:\RunHiddenConsole.exe C:\php8\php-cgi.exe -b 127.0.0.1:9999

    ECHO Starting NGINX
    start nginx.exe

    popd
    EXIT /b

Create file "nginx-stop.bat", edit with this

    @ECHO OFF
    taskkill /f /IM nginx.exe
    taskkill /f /IM php-cgi.exe
    EXIT /b

Create file "nginx-restart.bat"

    @ECHO OFF
    call nginx-stop.bat
    call nginx-start.bat
    EXIT /b

Test

Doble click on "nginx-start.bat"
Open your browser if every thing work you can see like this
Create folder like "test-php" in "C:\www"
Create file "index.php"
```
 <?php phpinfo(); ?>
```
Open your browser and go to "localhost/test-php"
If every thing ok you can see
At the end , nginx php now working.

Notes:
Sometimes , nginx & php cannot working properly if your run with nginx-start.bat
so you need to run php manually
open your terminal, run your php "php-cgi -b 127.0.0.1:9999"
and now your nginx & php work properly

Change Windows Terminal Theme

ilhamsabir — Mon, 22 Mar 2021 06:29:57 +0000

The Windows Terminal is a modern, fast, efficient, powerful, and productive terminal application for users of command-line tools and shells like Command Prompt, PowerShell, and WSL. Its main features include multiple tabs, panes, Unicode and UTF-8 character support, a GPU accelerated text rendering engine, and custom themes, styles, and configurations.

But to make windows terminal look beauty we need to add a theme, so lets start.

#First

Install Windows Terminal from Microsoft Store, Go to Store

#Second

Install Install Modules Oh-my-Posh

 Install-Module posh-git -Scope CurrentUser
 Install-Module oh-my-posh -Scope CurrentUser

#Third

Create *Powershell Profile *
```
 // use vscode
 code $PROFILE
```

Add this on your profile

 Import-Module posh-git
 Import-Module oh-my-posh

Import theme, to pick a theme check here, after that import on your profile

 Import-Module posh-git
 Import-Module oh-my-posh

 # your theme
 Set-PoshPrompt -Theme paradox

#Fourth

Customize your windows terminal color, open your terminal , and click setting.

Add this style object on "schemes"

 "schemes": [
    {
        "name": "CustomeTheme",
        "black": "#7d8b8f",
        "red": "#b23a52",
        "green": "#789b6a",
        "yellow": "#b9ac4a",
        "blue": "#225a79",
        "purple": "#bd4f5a",
        "cyan": "#2b7c71",
        "white": "#d2d8d9",
        "brightBlack": "#888888",
        "brightRed": "#f24840",
        "brightGreen": "#80c470",
        "brightYellow": "#ffeb62",
        "brightBlue": "#4196ff",
        "brightPurple": "#fc5275",
        "brightCyan": "#53cdbd",
        "brightWhite": "#d2d8d9",
        "background": "#2b2d2e",
        "foreground": "#d2d8d9",
        "selectionBackground": "#e4e8ed",
        "cursorColor": "#708284"
    }
],

On list , add that theme

  "list":
    [
        {
            // Make changes here to the powershell.exe profile.
            "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
            "name": "Windows PowerShell",
            "commandline": "powershell.exe",
            "hidden": false,
            "fontFace": "Fira Code",
            "fontSize": 9,
            "colorScheme": "CustomeTheme"
        },
        {
            // Make changes here to the cmd.exe profile.
            "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
            "name": "Command Prompt",
            "commandline": "cmd.exe",
            "hidden": false
        },
        {
            "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
            "hidden": false,
            "name": "Azure Cloud Shell",
            "source": "Windows.Terminal.Azure"
        }
    ]

Save it, and reload your terminal

Notes

You can change your theme color, by open

 $Home\[My ]Documents\WindowsPowerShell\Modules\oh-my-posh\3.118.0\themes

Select your active theme and edit that json.