Forem: johanputra

WireGuard Setup for Ubuntu Server (Laptop to be Remote Accessed)

johanputra — Tue, 03 Feb 2026 05:05:11 +0000

Step 1: Install WireGuard

# Update system
sudo apt update && sudo apt upgrade -y

# Install WireGuard
sudo apt install wireguard resolvconf -y

Step 2: Generate Server Key Pair

# Navigate to WireGuard directory
cd /etc/wireguard/

# Generate private key and save
sudo umask 077
wg genkey | sudo tee privatekey | wg pubkey | sudo tee publickey

# Display keys (save these securely)
echo "=== SERVER PRIVATE KEY ==="
sudo cat privatekey
echo -e "\n=== SERVER PUBLIC KEY ==="
sudo cat publickey

Save both keys in a secure location!

Step 3: Create Server Configuration

Create configuration file:

sudo nano /etc/wireguard/wg0.conf

Add the following content (replace [SERVER_PRIVATE_KEY] with your private key from Step 2):

[Interface]
PrivateKey = [SERVER_PRIVATE_KEY]
Address = 10.8.0.1/24
ListenPort = 51820
SaveConfig = true

# DNS configuration
DNS = 1.1.1.1, 8.8.8.8

# Firewall and routing rules
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

Example with actual values:

[Interface]
PrivateKey = ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890abcdef=
Address = 10.8.0.1/24
ListenPort = 51820
SaveConfig = true
DNS = 1.1.1.1, 8.8.8.8
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

Step 4: Enable IP Forwarding

# Edit sysctl configuration
sudo nano /etc/sysctl.conf

# Uncomment or add this line:
net.ipv4.ip_forward=1

# Apply changes
sudo sysctl -p

Step 5: Configure Firewall

# Allow WireGuard port
sudo ufw allow 51820/udp

# Allow SSH (don't forget!)
sudo ufw allow ssh

# Enable UFW
sudo ufw enable

# Check status
sudo ufw status

Step 6: Start WireGuard Service

# Start WireGuard interface
sudo wg-quick up wg0

# Enable auto-start on boot
sudo systemctl enable wg-quick@wg0

# Check status
sudo wg show

Step 7: Generate Client Configuration

7.1 Generate Client Keys

# Generate client keys
wg genkey | tee client_private.key
cat client_private.key | wg pubkey > client_public.key

echo "=== CLIENT PRIVATE KEY ==="
cat client_private.key
echo -e "\n=== CLIENT PUBLIC KEY ==="
cat client_public.key

7.2 Add Client to Server

# Add client to server configuration
sudo wg set wg0 peer $(cat client_public.key) allowed-ips 10.8.0.2/32

# Save configuration permanently
sudo wg-quick save wg0

7.3 Create Client Config File

Create ubuntu-client.conf file:

[Interface]
PrivateKey = [CLIENT_PRIVATE_KEY]
Address = 10.8.0.2/24
DNS = 1.1.1.1, 8.8.8.8

[Peer]
PublicKey = [SERVER_PUBLIC_KEY]
Endpoint = [SERVER_IP]:51820
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 25

How to get SERVER_IP:

# For public IP (if you have one)
curl -4 ifconfig.me

# For local IP
ip addr show | grep inet

Step 8: Enable Services for Remote Access

8.1 Enable SSH (if not already enabled)

# Install SSH server if not present
sudo apt install openssh-server -y

# Enable SSH service
sudo systemctl enable ssh
sudo systemctl start ssh

# Check status
sudo systemctl status ssh

8.2 Optional: Enable VNC for GUI access

# Install VNC server
sudo apt install x11vnc -y

# Set VNC password
x11vnc -storepasswd

# Create VNC service
sudo nano /etc/systemd/system/x11vnc.service

Service file content:

[Unit]
Description=x11vnc service
After=display-manager.service network.target syslog.target

[Service]
Type=simple
ExecStart=/usr/bin/x11vnc -forever -display :0 -auth guess -passwd /home/$(whoami)/.vnc/passwd
ExecStop=/usr/bin/killall x11vnc
Restart=on-failure

[Install]
WantedBy=multi-user.target

# Enable VNC service
sudo systemctl daemon-reload
sudo systemctl enable x11vnc
sudo systemctl start x11vnc

Step 9: Testing

9.1 Test WireGuard Server

# Check interface
ip addr show wg0

# Check WireGuard status
sudo wg show

# Test port listening
sudo netstat -tulnp | grep 51820

9.2 Test from Client

After setting up the client, test the connection:

# Ping server
ping 10.8.0.1

# SSH through VPN
ssh username@10.8.0.1

Step 10: Automated Setup Script

Create setup-wireguard-ubuntu.sh file:

#!/bin/bash

echo "=== WireGuard Auto Setup for Ubuntu ==="

# Install dependencies
sudo apt update
sudo apt install wireguard resolvconf -y

# Generate keys
cd /etc/wireguard
sudo umask 077
sudo wg genkey | sudo tee privatekey | sudo wg pubkey | sudo tee publickey

SERVER_PRIVATE_KEY=$(sudo cat privatekey)
SERVER_PUBLIC_KEY=$(sudo cat publickey)

# Create config
sudo tee /etc/wireguard/wg0.conf > /dev/null <<EOF
[Interface]
PrivateKey = $SERVER_PRIVATE_KEY
Address = 10.8.0.1/24
ListenPort = 51820
SaveConfig = true
DNS = 1.1.1.1, 8.8.8.8
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
EOF

# Enable IP forwarding
echo 'net.ipv4.ip_forward=1' | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

# Setup firewall
sudo ufw allow 51820/udp
sudo ufw allow ssh

# Start service
sudo wg-quick up wg0
sudo systemctl enable wg-quick@wg0

echo "=== Setup Complete! ==="
echo "Server Public Key: $SERVER_PUBLIC_KEY"
echo "WireGuard interface: wg0"
echo "Server VPN IP: 10.8.0.1"

Make executable and run:

chmod +x setup-wireguard-ubuntu.sh
sudo ./setup-wireguard-ubuntu.sh

Step 11: Management Commands

Useful commands:

# Start/Stop WireGuard
sudo wg-quick up wg0
sudo wg-quick down wg0

# Check status
sudo wg show
sudo systemctl status wg-quick@wg0

# View logs
sudo journalctl -u wg-quick@wg0 -f

# Add client manually
sudo wg set wg0 peer [CLIENT_PUBLIC_KEY] allowed-ips 10.8.0.2/32

# Remove client
sudo wg set wg0 peer [CLIENT_PUBLIC_KEY] remove

Troubleshooting

If you encounter issues:

# Restart service
sudo wg-quick down wg0
sudo wg-quick up wg0

# Check kernel module
lsmod | grep wireguard

# Check firewall
sudo ufw status

# Check routing
ip route show

# Check interface status
ip link show wg0

Common Issues and Solutions:

Interface not starting:

   # Check if module is loaded
   sudo modprobe wireguard

   # Check for errors in config
   sudo wg-quick down wg0
   sudo wg-quick up wg0

Connection issues:

   # Check if port is open
   sudo ufw status

   # Verify keys match
   sudo wg show

No internet access through VPN:

   # Check IP forwarding
   cat /proc/sys/net/ipv4/ip_forward

   # Check NAT rules
   sudo iptables -t nat -L

With this setup, your Ubuntu laptop is ready to be securely accessed remotely through WireGuard VPN connection!

Performance Tuning PHP

johanputra — Tue, 05 Aug 2025 01:56:30 +0000

PHP-FPM Pool Configuration (`www.conf`) - Performance Tuning

This document outlines the key parameters within a PHP-FPM pool configuration, essential for tuning PHP performance and managing server resources effectively.

Parameter Explanations

`pm = dynamic`

This parameter defines the process manager mode. dynamic mode allows PHP-FPM to automatically adjust the number of worker processes based on server load.

static: A fixed number of processes is used, as defined by pm.max_children.
dynamic: Processes scale up or down between min_spare_servers and max_children.
ondemand: Processes are created only when a request arrives and are terminated after a period of inactivity.

The dynamic mode, which you are using, requires additional parameters for configuration.

`pm.max_children = 1000`

This is the maximum number of simultaneous PHP worker processes. A high value like 1000 poses a significant risk of memory exhaustion (Out of Memory errors) and server crashes if not appropriately calculated.

Calculation:

To estimate the necessary RAM, multiply the number of processes by the average memory usage per process.
For example, 1000 processes × 100MB/process would require approximately 100GB of RAM.
Recommendation: This value should be carefully calculated based on your server's available RAM, leaving some overhead for the operating system and other services.

`pm.start_servers = 80`

The number of worker processes launched when the PHP-FPM service starts. This pre-spawns workers to handle an initial high load immediately.

`pm.min_spare_servers = 40`

The minimum number of idle worker processes kept running. Maintaining a minimum pool of spare servers reduces the time it takes to serve new requests.

`pm.max_spare_servers = 120`

The maximum number of idle worker processes. If the number of idle processes exceeds this value, PHP-FPM will terminate them to free up resources.

`request_terminate_timeout = 300s`

This parameter defines the maximum execution time for a single request. If a request exceeds 300 seconds (5 minutes), the process is automatically terminated. This is a critical setting for preventing hung or slow-running scripts from consuming resources indefinitely.

`request_slowlog_timeout = 5s`

Any script that takes longer than 5 seconds to execute will be logged for analysis.

`slowlog = /var/log/php-fpm/slowlog.log`

The file path where slow-executing scripts are logged. This log is essential for debugging application performance bottlenecks.

Best Practices and Recommendations

A configuration with pm.max_children = 1000 is typically unsuitable for servers with less than 100GB of RAM. A more balanced and safer configuration should be based on your server's hardware specifications.

Example Configuration for an 8GB RAM Server

pm = dynamic
pm.max_children = 50
pm.start_servers = 10
pm.min_spare_servers = 5
pm.max_spare_servers = 20

request_terminate_timeout = 300s
request_slowlog_timeout = 5s
slowlog = /var/log/php-fpm/slowlog.log

Note: Using 80% of available RAM reserves resources for the OS and other critical services.

Install zsh with autosuggestion in amazon linux

johanputra — Mon, 23 Jun 2025 08:05:05 +0000

To install zsh and Oh My Zsh with the suggestion plugin on Amazon Linux, follow these steps:

#!/bin/sh

# Install zsh
sudo yum install git zsh -y
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

# Install zsh-syntax-highlighting plugin
git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

# Install zsh-autosuggestions plugin
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions
echo "plugins=(zsh-syntax-highlighting zsh-autosuggestions)" >> ~/.zshrc

echo "source ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh" >> ~/.zshrc
echo "ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE='fg=blue'" >> ~/.zshrc
echo "ZSH_AUTOSUGGEST_USE_ASYNC=true" >> ~/.zshrc


source ~/.zshrc
echo "Installation of zsh and Oh My Zsh with suggestion plugin complete!"

Install zsh:

sudo yum install zsh

Install Oh My Zsh:

sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

Install the zsh-syntax-highlighting plugin (required for the suggestion plugin):

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

Install the zsh-autosuggestions plugin (suggestion plugin):

git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

Add the plugins to your Oh My Zsh configuration file:

echo "plugins=(zsh-syntax-highlighting zsh-autosuggestions)" >> ~/.zshrc

Restart your terminal or run source ~/.zshrc to apply the changes.

Note: If you want to use the suggestion plugin with the default Oh My Zsh theme, you may need to add the following line to your ~/.zshrc file:

source ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh

Also, you can configure the suggestion plugin by adding the following lines to your ~/.zshrc file:

ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE='fg=blue'
ZSH_AUTOSUGGEST_USE_ASYNC=true

This will highlight the suggestions in blue and use asynchronous suggestions.

After installing and configuring the suggestion plugin, you can use it by typing a command and then pressing the → key (or Tab key) to accept the suggestion.

Finding the PHP Socket File

johanputra — Mon, 23 Jun 2025 04:21:06 +0000

When working with PHP, it's not uncommon to encounter issues with the socket file. The socket file is a crucial component that enables communication between PHP and the web server or other applications. In this article, we'll explore the ways to find the PHP socket file, even if it's not explicitly defined in the configuration.

Understanding the PHP Socket File

The PHP socket file is a file that allows PHP to communicate with the web server or other applications. It's usually located in the /var/run/php directory and has a name like php7.4-fpm.sock. The socket file is used by PHP-FPM (PHP FastCGI Process Manager) to manage the communication between PHP and the web server.

Locating the PHP Socket File

If you're having trouble finding the PHP socket file, here are some steps you can follow:

1 Using the netstat Command: The netstat command can be used to list all the open sockets on your system. You can use the following command to find the PHP socket file:

netstat -lp | grep sock

This command will list all the open sockets, and you can look for the one that corresponds to the PHP socket file.

2 Using the ss Command: The ss command is similar to the netstat command, but it provides more detailed information about the sockets. You can use the following command to find the PHP socket file:

ss -l | grep sock

This command will list all the open sockets, and you can look for the one that corresponds to the PHP socket file.

3 Using the lsof Command: The lsof command can be used to list all the open files on your system. You can use the following command to find the PHP socket file:

lsof | grep sock

This command will list all the open files, and you can look for the one that corresponds to the PHP socket file.

4 Using the find Command: The find command can be used to search for files on your system. You can use the following command to find the PHP socket file:

find / -name "*.sock"

This command will search for all files with the .sock extension, and you can look for the one that corresponds to the PHP socket file.

5 Checking the PHP-FPM Configuration: You can also check the PHP-FPM configuration file to see if the socket file is defined. The configuration file is usually located in the /etc/php/7.4/fpm directory. You can use the following command to find the socket file:

grep listen /etc/php/7.4/fpm/php-fpm.conf

This command will search for the listen directive in the configuration file, which should point to the socket file.

6 Checking the /var/run/php Directory: Finally, you can check the /var/run/php directory to see if the socket file is located there. You can use the following command to list the files in the directory:

ls /var/run/php

This command will list all the files in the directory, and you can look for the one that corresponds to the PHP socket file.

Conclusion

Finding the PHP socket file can be a challenging task, but by following the steps outlined in this article, you should be able to locate it. Remember to use the netstat, ss, lsof, and find commands to search for the socket file, and check the PHP-FPM configuration file and the /var/run/php directory for more information. With this knowledge, you'll be able to troubleshoot issues with the PHP socket file and get your application up and running smoothly.

Monitor container with Portainer

johanputra — Wed, 26 Jun 2024 10:09:29 +0000

membuat volume

docker volume create portainer_data

perintah docker run yang digunakan untuk membuat portainer

docker run -d \
  -p 8000:8000 \
  -p 9443:9443 \
  --name portainer \
  --restart=unless-stopped \
  --network <network> \
  -v /var/run/docker.sock:/var/run/docker.sock  \
  -v portainer_data:/data \
  portainer/portainer-ce:2.20.3-alpine

penjelasan untuk setiap perintah docker run

docker run: Perintah untuk membuat dan menjalankan container baru.
-d: Menjalankan container di background (mode detached).
-p 8000:8000: Memetakan port 8000 pada host ke port 8000 pada container. Ini digunakan untuk akses HTTP.
-p 9443:9443: Memetakan port 9443 pada host ke port 9443 pada container. Ini digunakan untuk akses HTTPS.
--name portainer: Menetapkan nama container menjadi portainer.
--restart=unless-stopped: Mengatur kebijakan restart container. Dengan opsi ini, container akan otomatis restart kecuali jika secara eksplisit dihentikan.
-v /var/run/docker.sock:/var/run/docker.sock: Memetakan socket Docker dari host ke container. Ini memungkinkan Portainer untuk berinteraksi dengan Docker daemon pada host.
-v portainer_data:/data: Membuat volume bernama portainer_data dan memetakannya ke /data di dalam container. Ini digunakan untuk persistensi data Portainer, memastikan data tetap ada meskipun container dihapus atau diperbarui.
portainer/portainer-ce:2.20.3-alpine: Menentukan image yang akan digunakan untuk container. Dalam hal ini, menggunakan versi 2.20.3 dari Portainer Community Edition yang berbasis Alpine Linux.

nginx konfigurasi untuk menampilkan antarmuka portainer:

server {
    server_name portainer.martabanggosong.com; 

    location / {
        proxy_pass http://localhost:9000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Langkah-langkah untuk mengaplikasikan konfigurasi ini:

1 Buat file konfigurasi baru di direktori konfigurasi Nginx (biasanya /etc/nginx/sites-available/) dengan nama portainer.conf dan masukkan konfigurasi di atas.
2 Sesuaikan server_name dengan domain Anda dan pastikan proxy_pass mengarah ke alamat tempat Portainer berjalan.
3 Buat symlink dari file konfigurasi yang Anda buat ke direktori /etc/nginx/sites-enabled/ untuk mengaktifkannya.

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

4 Test konfigurasi Nginx untuk memastikan tidak ada kesalahan.

sudo nginx -t

5 Reload Nginx untuk menerapkan perubahan.

sudo systemctl reload nginx

Install php in linux server

johanputra — Tue, 16 Jan 2024 07:08:08 +0000

sudo add-apt-repository ppa:ondrej/php
sudo apt update
sudo apt install php8.2-fpm php8.2-mysql php8.2-curl php8.2-xml php8.2-opcache php8.2-mbstring php8.2-zip

systemctl status php8.2-fpm.service
● php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager
     Loaded: loaded (/lib/systemd/system/php8.2-fpm.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-01-16 12:54:56 WIB; 1h 11min ago
       Docs: man:php-fpm8.2(8)
    Process: 1268 ExecStartPost=/usr/lib/php/php-fpm-socket-helper install /run/php/php-fpm.sock /etc/php/8.2/fpm/pool.d/www.conf 82 (code=exited, status=0/SUCCESS)
    Process: 14147 ExecReload=/bin/kill -USR2 $MAINPID (code=exited, status=0/SUCCESS)
   Main PID: 1102 (php-fpm8.2)
     Status: "Processes active: 0, idle: 2, Requests: 6, slow: 0, Traffic: 0req/sec"
      Tasks: 3 (limit: 9211)
     Memory: 62.1M
     CGroup: /system.slice/php8.2-fpm.service
             ├─ 1102 php-fpm: master process (/etc/php/8.2/fpm/php-fpm.conf)
             ├─14162 php-fpm: pool www
             └─14163 php-fpm: pool www

bind mount and volume

johanputra — Wed, 01 Nov 2023 10:25:22 +0000

Bind mounts and volumes are both used in Docker to share data between the host machine and the container. However, there are some differences between the two: Bind Mounts:

Bind mounts allow you to mount a file or directory on the host machine into a container.
Bind mounts can be read-write or read-only.
Bind mounts can be used to share data between the host machine and the container.
Bind mounts can be used to share data between containers.
Bind mounts can be used to access host level resources.

Volumes:

Volumes are managed by Docker and are created and managed by Docker commands.
Volumes can be used to persist data.
Volumes can be shared between containers.
Volumes can be backed up and restored.
Volumes can be used to improve performance.

In summary, bind mounts are used to share data between the host machine and the container, while volumes are used to persist data and improve performance. Both bind mounts and volumes have their own use cases and can be used together to achieve the desired outcome.

Managing Configuration Files with Chezmoi

johanputra — Sun, 17 Sep 2023 07:32:10 +0000

Managing Configuration Files with Chezmoi

Chezmoi is a powerful tool for managing dotfiles and personal configuration files in a consistent, reproducible, and version-controlled manner.

Official documentation:
https://www.chezmoi.io/

Installing Chezmoi

You can install Chezmoi by specifying a custom installation directory. The following command installs Chezmoi into $HOME/.local/bin:

sh -c "$(curl -fsLS get.chezmoi.io)" -- -b $HOME/.local/bin

Ensure that $HOME/.local/bin is included in your PATH.

Verifying the Installation

To confirm that Chezmoi has been installed successfully, check the version and binary location:

chezmoi --version

Example output:

chezmoi version v2.40.0, commit 6a8ca1634654734bb33a036ffb9c21e6b9f4d28d, built at 2023-09-19T09:56:08Z

Verify the binary path:

which chezmoi

Expected output:

/home/xyz/.local/bin/chezmoi

Adding Files to Chezmoi

To start managing configuration files, add them to Chezmoi. For example, to manage .zshrc and .vimrc:

chezmoi add ~/.zshrc ~/.vimrc

Chezmoi will copy these files into its source directory, which by default is:

/home/xyz/.local/share/chezmoi

This directory represents the source of truth for your dotfiles.

Pushing Chezmoi Configuration to GitHub

Navigate to the Chezmoi source directory and initialize or configure your Git repository:

cd ~/.local/share/chezmoi
git remote set-url origin git@github.com:user/dotfiles.git
git add .
git commit -m "Initial commit"
git push origin main

At this point, your dotfiles are safely version-controlled in GitHub.

Updating Managed Files

When you modify a managed file (for example, .zshrc) directly in your home directory, you need to reflect those changes back into Chezmoi’s source directory:

chezmoi add ~/.zshrc

This updates the corresponding file under ~/.local/share/chezmoi, after which you can commit and push the changes to Git.

Note:
chezmoi update is used to pull and apply changes from the remote repository to your local machine, not to capture local file changes into the repository.

Applying Configuration on a New Machine

On a new system, you can apply all managed configurations with:

chezmoi init git@github.com:user/dotfiles.git
chezmoi apply

This will recreate your dotfiles exactly as defined in the repository.

Conclusion

This article only covers the basic usage of Chezmoi, such as installation, adding files, and Git integration. Chezmoi also supports advanced features including:

Templates
Conditional configuration
Secrets management
Encrypted files
Cross-platform setups

Further exploration is recommended as your configuration management needs grow. Feel free to leave comments or suggestions, and we can continue learning and improving this setup together.

Install Go (Golang) on a Linux

johanputra — Tue, 29 Aug 2023 08:49:09 +0000

To install Go (Golang) on a Linux system, you can follow these steps:

Download Go: Open a terminal window and use the wget command to download the Go installation package. You can find the latest version of Go on the official Golang download page.

For example, to download Go version 1.17, you can use:

   wget https://golang.org/dl/go1.17.linux-amd64.tar.gz

Extract the Archive: After downloading, you need to extract the downloaded archive. Use the tar command to extract it:

   tar -xvf go1.17.linux-amd64.tar.gz

Move Go: Move the extracted Go directory to a location on your system. Traditionally, it's placed in the /usr/local directory. You'll need superuser (root) privileges for this:

   sudo mv go /usr/local

Set Environment Variables: You need to set some environment variables to let your system know where Go is installed and where your Go workspace (where you'll develop your Go programs) is located. Add the following lines to your shell profile configuration file (e.g., ~/.bashrc, ~/.zshrc, or ~/.profile):

   export GOPATH=$HOME/go
   export PATH=/usr/local/go/bin:$PATH:$GOPATH/bin

Then, apply the changes to your current shell session:

   source ~/.zshrc ~/.bashrc  # or the appropriate configuration file

Verify Installation: You can now verify that Go is installed correctly by opening a new terminal window and typing:

   go version

go1.17 linux/amd64

You should see the installed Go version printed in the output.

Perbedaan flag --q -q -qq di unzip

johanputra — Tue, 22 Aug 2023 09:40:23 +0000

Flag --q, -q, dan -qq dalam perintah unzip merujuk pada level verbosity atau tampilan pesan yang ditampilkan selama proses ekstrak. Perbedaan dari masing-masing flag:

--q (Quiet): Ini adalah flag yang dapat digunakan untuk mengurangi keluaran atau pesan selama proses ekstrak. Ketika flag --q digunakan, unzip hanya akan menampilkan pesan kesalahan atau peringatan yang penting. Pesan normal dan informasi ekstra tidak akan ditampilkan.

Contoh: unzip --q file.zip

-q (Quiet): Ini adalah bentuk pendek dari flag --q. Penggunaan dan efeknya sama seperti yang dijelaskan di atas.

Contoh: unzip -q file.zip

-qq (Really Quiet): Ini adalah bentuk yang lebih diam daripada -q. Saat menggunakan flag -qq, unzip hanya akan menampilkan pesan kesalahan yang sangat penting dan tidak akan menampilkan pesan peringatan apa pun.

Contoh: unzip -qq file.zip

Contoh penggunaan rsync

johanputra — Mon, 21 Aug 2023 07:54:24 +0000

cover image

1. Menyalin File dari Lokal ke Remote Server dengan SSH

Deskripsi: Menyalin file source_file.txt dari mesin lokal ke direktori /home/remoteuser/destination/ di remote server melalui koneksi SSH.

rsync -avz -e "ssh -p 22" source_file.txt remoteuser@remote.example.com:/home/remoteuser/destination/

2. Menyalin Folder Lokal ke Remote Server dengan SSH

Deskripsi: Menyalin seluruh isi folder local_folder/ dari mesin lokal ke direktori /home/remoteuser/destination/ di remote server melalui koneksi SSH.

rsync -avz -e "ssh -p 22" local_folder/ remoteuser@remote.example.com:/home/remoteuser/destination/

3. Menyalin File dari Remote Server ke Lokal dengan SSH

Deskripsi: Menyalin file remote_file.txt dari direktori /home/remoteuser/source/ di remote server ke direktori lokal /path/to/local/destination/ melalui koneksi SSH.

rsync -avz -e "ssh -p 22" remoteuser@remote.example.com:/home/remoteuser/source/remote_file.txt /path/to/local/destination/

4. Menyalin File melalui RSH

Deskripsi: Menyalin file source_file.txt dari mesin lokal ke direktori /home/remoteuser/destination/ di remote server melalui RSH (Remote Shell).

rsync -avz --rsh=rsh source_file.txt remoteuser@remote.example.com:/home/remoteuser/destination/

5. Menyalin File dengan Filter Kustom

Deskripsi: Menyalin file-file yang memiliki ekstensi .jpg dari source_folder/ ke destination_folder/.

rsync -avz --include="*.jpg" --exclude="*" source_folder/ destination_folder/

6. Menyalin dengan Opsi Dry Run

Deskripsi: Melakukan simulasi tanpa benar-benar menyalin file, hanya menampilkan apa yang akan terjadi.

rsync -avz --dry-run source_folder/ destination_folder/

7. Menyalin dengan Hapus File di Tujuan

Deskripsi: Menyalin seluruh isi folder local_folder/ dari mesin lokal ke remote_folder/ di remote server, dan menghapus file di tujuan yang tidak ada di sumber.

rsync -avz --delete local_folder/ remote_folder/

8. Menyalin dengan Exclude dari File

Deskripsi: Menyalin file-file dari source_folder/ ke destination_folder/, tetapi mengabaikan file yang ada dalam exclude_list.txt.

rsync -avz --exclude-from="exclude_list.txt" source_folder/ destination_folder/

9. Menyalin dengan Opsi Compression

Deskripsi: Menyalin file source_file.txt dari mesin lokal ke direktori /home/remoteuser/destination/ di remote server dengan kompresi selama transfer.

rsync -avz -e "ssh -p 22" --compress source_file.txt remoteuser@remote.example.com:/home/remoteuser/destination/

10. Menyalin dengan SSH dan Ekspresi Reguler

Deskripsi: Menyalin file-file yang memiliki ekstensi .txt dari source_folder/ ke destination_folder/ di remote server dengan koneksi SSH.

rsync -avz -e "ssh -p 22" source_folder/ remoteuser@remote.example.com:/home/remoteuser/destination/ --include="*.txt" --exclude="*"

Contoh penggunaan `sync`

johanputra — Sat, 19 Aug 2023 13:11:37 +0000

Pada sistem operasi Linux, perintah sync digunakan untuk memastikan bahwa data dalam buffer sistem ditulis ke perangkat penyimpanan fisik seperti disk. Ini memastikan bahwa data yang ada dalam buffer benar-benar tertulis ke media penyimpanan sebelum operasi penting dilakukan. Berikut adalah beberapa contoh penggunaan perintah sync:

Sebelum Mematikan atau Me-restart Sistem: Sebelum mematikan atau me-restart sistem, disarankan untuk menggunakan sync untuk memastikan semua data yang ada dalam buffer ditulis ke disk. Ini akan membantu mencegah kehilangan data yang belum disimpan.

   sync

Sebelum Mencabut Media Penyimpanan Eksternal: Jika Anda memiliki perangkat penyimpanan eksternal seperti USB drive yang terhubung ke sistem, gunakan sync sebelum mencabutnya. Ini akan memastikan bahwa semua data yang ada dalam buffer ditulis ke perangkat sebelum dicabut.

   sync

Setelah Menjalankan Perintah Pengelolaan Disk: Setelah menjalankan perintah untuk mengelola partisi atau sistem berkas (seperti fdisk, parted, atau mkfs), gunakan sync untuk memastikan bahwa perubahan yang Anda buat telah diterapkan pada media penyimpanan.

   parted /dev/sdX mklabel gpt
   sync

Sebelum Penggunaan dd untuk Menyalin Data: Jika Anda menggunakan perintah dd untuk menyalin data dari atau ke perangkat penyimpanan, gunakan sync setelah selesai untuk memastikan bahwa semua data telah ditulis sepenuhnya.

   dd if=/dev/sda of=/dev/sdb
   sync

Sebelum Melihat Informasi Disk: Jika Anda ingin melihat informasi terbaru tentang disk dan partisi menggunakan perintah seperti lsblk atau fdisk, pastikan untuk menggunakan sync terlebih dahulu untuk memastikan data terbaru ditampilkan.

   sync
   lsblk

Penting untuk diingat bahwa sync adalah perintah yang cepat dan tidak menghasilkan output. Ini hanya memastikan bahwa data dalam buffer ditulis ke perangkat penyimpanan. Pastikan untuk menggunakan sync dalam situasi yang tepat untuk memastikan integritas data Anda.

Forem: johanputra

WireGuard Setup for Ubuntu Server (Laptop to be Remote Accessed)

Step 1: Install WireGuard

Step 2: Generate Server Key Pair

Step 3: Create Server Configuration

Step 4: Enable IP Forwarding

Step 5: Configure Firewall

Step 6: Start WireGuard Service

Step 7: Generate Client Configuration

7.1 Generate Client Keys

7.2 Add Client to Server

7.3 Create Client Config File

Step 8: Enable Services for Remote Access

8.1 Enable SSH (if not already enabled)

8.2 Optional: Enable VNC for GUI access

Step 9: Testing

9.1 Test WireGuard Server

9.2 Test from Client

Step 10: Automated Setup Script

Step 11: Management Commands

Useful commands:

Troubleshooting

If you encounter issues:

Common Issues and Solutions:

Performance Tuning PHP

PHP-FPM Pool Configuration (www.conf) - Performance Tuning

Parameter Explanations

pm = dynamic

pm.max_children = 1000

pm.start_servers = 80

pm.min_spare_servers = 40

pm.max_spare_servers = 120

request_terminate_timeout = 300s

request_slowlog_timeout = 5s

slowlog = /var/log/php-fpm/slowlog.log

Best Practices and Recommendations

Example Configuration for an 8GB RAM Server

Install zsh with autosuggestion in amazon linux

Finding the PHP Socket File

Monitor container with Portainer

Install php in linux server

bind mount and volume

Managing Configuration Files with Chezmoi

Managing Configuration Files with Chezmoi

Installing Chezmoi

Verifying the Installation

Adding Files to Chezmoi

Pushing Chezmoi Configuration to GitHub

Updating Managed Files

Applying Configuration on a New Machine

Conclusion

Install Go (Golang) on a Linux

Perbedaan flag --q -q -qq di unzip

Contoh penggunaan rsync

1. Menyalin File dari Lokal ke Remote Server dengan SSH

2. Menyalin Folder Lokal ke Remote Server dengan SSH

3. Menyalin File dari Remote Server ke Lokal dengan SSH

4. Menyalin File melalui RSH

5. Menyalin File dengan Filter Kustom

6. Menyalin dengan Opsi Dry Run

7. Menyalin dengan Hapus File di Tujuan

8. Menyalin dengan Exclude dari File

9. Menyalin dengan Opsi Compression

10. Menyalin dengan SSH dan Ekspresi Reguler

Contoh penggunaan `sync`

PHP-FPM Pool Configuration (`www.conf`) - Performance Tuning

`pm = dynamic`

`pm.max_children = 1000`

`pm.start_servers = 80`

`pm.min_spare_servers = 40`

`pm.max_spare_servers = 120`

`request_terminate_timeout = 300s`

`request_slowlog_timeout = 5s`

`slowlog = /var/log/php-fpm/slowlog.log`