Skip to content
BranchesTags

Repository files navigation

toolsh 🛠️

Kumpulan script dan Docker image untuk persiapan, manajemen, dan otomasi server Linux.

📦 Daftar Tools

Tool Tipe Deskripsi
setup-swap.sh Shell Script Setup swap memory di server
setup-domain-nginx.sh Shell Script Setup domain Nginx + SSL Let's Encrypt
pg_clone.sh Shell Script Clone database PostgreSQL antar server via remote
k3s-uninstall.sh Shell Script Uninstall K3s server secara menyeluruh
pg-dump-to-r2 Docker Image Dump PostgreSQL → gzip → upload ke Cloudflare R2 / S3
r2-to-pg Docker Image Restore PostgreSQL dari Cloudflare R2 / S3 → gunzip → psql

setup-swap.sh

Setup swap memory pada server Linux.

sudo curl -fsSL https://raw.githubusercontent.com/abilfida/toolsh/main/setup-swap.sh | sudo bash

setup-domain-nginx.sh

Setup pointing domain ke Nginx sebagai reverse proxy atau static file server, sekaligus install SSL otomatis via Let's Encrypt (Certbot).

Fitur:

  • Install & konfigurasi Nginx otomatis
  • Support reverse proxy ke port aplikasi
  • Install SSL Let's Encrypt dengan Certbot
  • Setup auto-renewal SSL via cron (setiap hari jam 03:00)

Usage:

sudo curl -fsSL https://raw.githubusercontent.com/abilfida/toolsh/main/setup-domain-nginx.sh \\
  | sudo bash -s -- <domain> <email> [port]

Contoh:

# Reverse proxy ke aplikasi di port 3000
sudo curl -fsSL https://raw.githubusercontent.com/abilfida/toolsh/main/setup-domain-nginx.sh \\
  | sudo bash -s -- myapp.com admin@myapp.com 3000

# Static file / web root (port 80)
sudo curl -fsSL https://raw.githubusercontent.com/abilfida/toolsh/main/setup-domain-nginx.sh \\
  | sudo bash -s -- myapp.com admin@myapp.com

Parameter:

Parameter Wajib Keterangan
domain ✅ Domain yang akan di-setup (contoh: myapp.com)
email ✅ Email untuk notifikasi SSL Let's Encrypt
port ❌ Port aplikasi untuk reverse proxy (default: 80)

pg_clone.sh

Clone seluruh database PostgreSQL dari server origin ke server clone melalui koneksi remote. Script dijalankan dari server tujuan (clone), menembak langsung ke server sumber (origin).

Fitur:

  • Dump otomatis dari server origin via pg_dump custom format
  • Drop & recreate database tujuan sebelum restore
  • Memutus koneksi aktif ke DB tujuan sebelum drop
  • Restore paralel dengan pg_restore --jobs
  • Verifikasi jumlah tabel setelah clone selesai
  • Konfirmasi interaktif sebelum eksekusi (safety guard)

Flow:

[Server Clone] ──── pg_dump remote ───► [Server Origin]
       │
   dump file ◄──────────┘
       │
  pg_restore (lokal)
       │
   DB Clone ✅

Cara pakai:

Edit variabel konfigurasi di bagian atas script, lalu jalankan:

# Download script
curl -fsSL https://raw.githubusercontent.com/abilfida/toolsh/main/pg_clone.sh -o pg_clone.sh
chmod +x pg_clone.sh

# Jalankan dari server clone
./pg_clone.sh

Variabel konfigurasi:

# Server Origin (sumber)
ORIGIN_HOST="192.168.1.100"
ORIGIN_PORT="5432"
ORIGIN_USER="postgres"
ORIGIN_PASSWORD="yourpassword"
ORIGIN_DB="yourdb"

# Server Clone / Lokal (tujuan)
CLONE_HOST="127.0.0.1"
CLONE_PORT="5432"
CLONE_USER="postgres"
CLONE_PASSWORD="yourpassword"
CLONE_DB="yourdb_clone"

Tips: Untuk database besar pada koneksi remote, jalankan pg_dump langsung di server origin lalu transfer file dump ke server clone untuk menghindari TCP timeout.

k3s-uninstall.sh

Uninstall K3s server secara menyeluruh — stop service, hapus binary, bersihkan network interface, hapus semua direktori residual, termasuk opsi drain agent node untuk cluster multi-node.

Fitur:

  • Konfirmasi interaktif sebelum eksekusi (safety guard)
  • Drain & delete agent/worker node dari cluster (opsional, untuk multi-node)
  • Jalankan uninstall script bawaan K3s secara otomatis
  • Bersihkan semua direktori residual: /var/lib/rancher/k3s, /etc/rancher/k3s, /run/k3s, /run/flannel, /var/lib/kubelet, /var/lib/cni
  • Opsi reboot otomatis setelah uninstall selesai
  • Output berwarna (info, sukses, peringatan, error)

Cara pakai:

# Jalankan langsung via curl
curl -fsSL https://raw.githubusercontent.com/abilfida/toolsh/main/k3s-uninstall.sh | sudo bash

Atau download lalu jalankan manual:

wget -O k3s-uninstall.sh https://raw.githubusercontent.com/abilfida/toolsh/main/k3s-uninstall.sh
chmod +x k3s-uninstall.sh
sudo ./k3s-uninstall.sh

Langkah yang dijalankan script:

Langkah Aksi
1 Drain & hapus agent/worker node (opsional, multi-node)
2 Jalankan /usr/local/bin/k3s-uninstall.sh bawaan K3s
3 Bersihkan semua direktori residual
4 Reboot server (opsional, direkomendasikan)

⚠️ Perhatian: Script ini tidak menghapus data dari external datastore (misal: PostgreSQL eksternal) maupun data dari Kubernetes Persistent Volumes yang dibuat oleh pod.

pg-dump-to-r2 (Docker Image)

Docker image untuk backup PostgreSQL secara otomatis: dump → gzip → upload ke Cloudflare R2 atau S3-compatible Object Storage.

✨ Fitur v5 — Zero Disk Usage

  • Streaming pipeline — pg_dump | gzip | rclone rcat langsung ke R2 tanpa tulis ke disk
  • Disk usage: 0 bytes (sebelumnya: ~2x ukuran database)
  • PostgreSQL 18 client support (install via PGDG official APT repo)
  • TCP keepalive built-in untuk koneksi remote yang stabil
  • Retensi otomatis: hapus file backup lama di R2
  • Version check otomatis pg_dump vs server PostgreSQL
  • Logging versi semua tools untuk diagnosis
  • Support linux/amd64 dan linux/arm64

Image:

ghcr.io/abilfida/toolsh/pg-dump-to-r2:latest

Cara Pakai

1. Buat file .env:

cp pg-dump-to-r2/.env.example .env
# Edit .env sesuai konfigurasi
# Database
DB_HOST=127.0.0.1
DB_PORT=5432
DB_USER=your_db_user
DB_PASSWORD=your_db_password
DB_NAME=your_db_name

# TCP Keepalive (opsional - untuk koneksi remote)
DB_KEEPALIVES=1
DB_KEEPALIVES_IDLE=30
DB_KEEPALIVES_INTERVAL=10
DB_KEEPALIVES_COUNT=5
DB_CONNECT_TIMEOUT=30

# Cloudflare R2
R2_ACCOUNT_ID=your_cloudflare_account_id
R2_ACCESS_KEY_ID=your_r2_access_key_id
R2_SECRET_ACCESS_KEY=your_r2_secret_access_key
R2_BUCKET=your-bucket-name
R2_PREFIX=pg-backups

# Opsi backup (opsional)
COMPRESS_LEVEL=6
RETENTION_DAYS=7

2. Jalankan:

docker run --rm --env-file .env --network host \\
  ghcr.io/abilfida/toolsh/pg-dump-to-r2:latest

Atau inline dengan -e:

docker run --rm \\
  -e DB_HOST=127.0.0.1 \\
  -e DB_USER=myuser \\
  -e DB_PASSWORD=mypassword \\
  -e DB_NAME=mydb \\
  -e R2_ACCOUNT_ID=xxxx \\
  -e R2_ACCESS_KEY_ID=xxxx \\
  -e R2_SECRET_ACCESS_KEY=xxxx \\
  -e R2_BUCKET=my-bucket \\
  --network host \\
  ghcr.io/abilfida/toolsh/pg-dump-to-r2:latest

Kubernetes CronJob

apiVersion: v1
kind: Secret
metadata:
  name: pg-dump-r2-secret
  namespace: default
type: Opaque
stringData:
  DB_HOST: "127.0.0.1"
  DB_PORT: "5432"
  DB_USER: "your_db_user"
  DB_PASSWORD: "your_db_password"
  DB_NAME: "your_db_name"
  R2_ACCOUNT_ID: "your_cf_account_id"
  R2_ACCESS_KEY_ID: "your_r2_key_id"
  R2_SECRET_ACCESS_KEY: "your_r2_secret"
  R2_BUCKET: "your-bucket"
  R2_PREFIX: "pg-backups"
  RETENTION_DAYS: "7"
---
apiVersion: batch/v1
kind: CronJob
metadata:
  name: pg-dump-to-r2
  namespace: default
spec:
  schedule: "0 2 * * *"  # Setiap hari jam 02:00
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: Never
          hostNetwork: true
          containers:
          - name: pg-dump-to-r2
            image: ghcr.io/abilfida/toolsh/pg-dump-to-r2:latest
            envFrom:
            - secretRef:
                name: pg-dump-r2-secret

Environment Variables

Variabel Default Wajib Keterangan
DB_HOST 127.0.0.1 — Host PostgreSQL
DB_PORT 5432 — Port PostgreSQL
DB_USER — ✅ Username PostgreSQL
DB_PASSWORD — ✅ Password PostgreSQL
DB_NAME — ✅ Nama database
DB_KEEPALIVES 1 — Enable TCP keepalive
DB_KEEPALIVES_IDLE 30 — Idle time (detik) sebelum kirim probe
DB_KEEPALIVES_INTERVAL 10 — Interval (detik) antar probe
DB_KEEPALIVES_COUNT 5 — Jumlah probe gagal sebelum putus
DB_CONNECT_TIMEOUT 30 — Timeout koneksi (detik)
DB_TCP_USER_TIMEOUT 60000 — TCP user timeout (milidetik)
R2_ACCOUNT_ID — ✅ Cloudflare Account ID
R2_ACCESS_KEY_ID — ✅ R2 API Access Key ID
R2_SECRET_ACCESS_KEY — ✅ R2 API Secret Access Key
R2_BUCKET — ✅ Nama bucket R2
R2_PREFIX pg-backups — Subfolder di dalam bucket
COMPRESS_LEVEL 6 — Level kompresi gzip (1–9)
RETENTION_DAYS 7 — Hapus file lebih dari N hari (0 = nonaktif)

Build dengan Versi PostgreSQL Spesifik

Jika server PostgreSQL kamu versi 16 atau 17, rebuild image dengan PG_MAJOR build arg:

# PostgreSQL 16
docker build --build-arg PG_MAJOR=16 -t pg-dump-to-r2:pg16 ./pg-dump-to-r2

# PostgreSQL 17
docker build --build-arg PG_MAJOR=17 -t pg-dump-to-r2:pg17 ./pg-dump-to-r2

# PostgreSQL 18 (default)
docker build -t pg-dump-to-r2:pg18 ./pg-dump-to-r2

Cara Restore dari R2

# 1. Download file dump dari R2 ke lokal
rclone copy \\
  ":s3,provider=Cloudflare,access_key_id=KEY,secret_access_key=SECRET,endpoint=https://ACCOUNT_ID.r2.cloudflarestorage.com:BUCKET/pg-backups/" \\
  /tmp/ --include "*.dump.gz"

# 2. Decompress + restore
gunzip -c /tmp/mydb_20260511_020000.dump.gz \\
  | PGPASSWORD="pass" psql \\
  -h 127.0.0.1 -U postgres -d mydb_restore

r2-to-pg (Docker Image)

Docker image untuk restore PostgreSQL secara otomatis: download dari Cloudflare R2 / S3-compatible Object Storage → gunzip → restore ke PostgreSQL.

✨ Fitur v1 — Zero Disk Usage

  • Streaming pipeline — rclone cat | gunzip | psql langsung tanpa tulis ke disk
  • Disk usage: 0 bytes — tidak ada file temporary
  • Auto-select backup — pilih file *.dump.gz terbaru dari R2 prefix
  • Explicit file option — restore file tertentu via R2_OBJECT
  • Clean restore mode — drop & recreate database sebelum restore
  • Post-restore ANALYZE — optional VACUUM ANALYZE untuk optimasi
  • PostgreSQL 18 client support (override via build arg)
  • TCP keepalive built-in untuk koneksi stabil
  • Support linux/amd64 dan linux/arm64

Image:

ghcr.io/abilfida/toolsh/r2-to-pg:latest

Cara Pakai

1. Buat file .env:

cp r2-to-pg/.env.example .env
# Edit .env sesuai konfigurasi
# Database Target
DB_HOST=127.0.0.1
DB_PORT=5432
DB_USER=your_db_user
DB_PASSWORD=your_db_password
DB_NAME=your_db_name
DB_ADMIN_DB=postgres

# Cloudflare R2
R2_ACCOUNT_ID=your_cloudflare_account_id
R2_ACCESS_KEY_ID=your_r2_access_key_id
R2_SECRET_ACCESS_KEY=your_r2_secret_access_key
R2_BUCKET=your-bucket-name
R2_PREFIX=pg-backups

# Opsional: restore file tertentu (kosong = auto-select terbaru)
R2_OBJECT=mydb_20260513_020000.dump.gz

# Opsi restore
CLEAN_BEFORE_RESTORE=true
CREATE_DB_IF_NOT_EXISTS=true
POST_RESTORE_ANALYZE=false

2. Jalankan:

docker run --rm --env-file .env --network host \
  ghcr.io/abilfida/toolsh/r2-to-pg:latest

Atau inline dengan -e:

docker run --rm \
  -e DB_HOST=127.0.0.1 \
  -e DB_USER=myuser \
  -e DB_PASSWORD=mypassword \
  -e DB_NAME=mydb \
  -e R2_ACCOUNT_ID=xxxx \
  -e R2_ACCESS_KEY_ID=xxxx \
  -e R2_SECRET_ACCESS_KEY=xxxx \
  -e R2_BUCKET=my-bucket \
  --network host \
  ghcr.io/abilfida/toolsh/r2-to-pg:latest

Restore Mode

Mode CLEAN_BEFORE_RESTORE Behavior
Clean true Drop database, terminate koneksi aktif, recreate, restore
Append false Restore ke database existing (data bisa duplicate)

Rekomendasi: Gunakan CLEAN_BEFORE_RESTORE=true untuk restore penuh dari backup.

Kubernetes Job (One-shot Restore)

apiVersion: v1
kind: Secret
metadata:
  name: r2-to-pg-secret
  namespace: default
type: Opaque
stringData:
  DB_HOST: "127.0.0.1"
  DB_PORT: "5432"
  DB_USER: "your_db_user"
  DB_PASSWORD: "your_db_password"
  DB_NAME: "your_db_name"
  DB_ADMIN_DB: "postgres"
  R2_ACCOUNT_ID: "your_cf_account_id"
  R2_ACCESS_KEY_ID: "your_r2_key_id"
  R2_SECRET_ACCESS_KEY: "your_r2_secret"
  R2_BUCKET: "your-bucket"
  R2_PREFIX: "pg-backups"
  CLEAN_BEFORE_RESTORE: "true"
---
apiVersion: batch/v1
kind: Job
metadata:
  name: r2-to-pg-restore
  namespace: default
spec:
  template:
    spec:
      restartPolicy: Never
      hostNetwork: true
      containers:
      - name: r2-to-pg
        image: ghcr.io/abilfida/toolsh/r2-to-pg:latest
        envFrom:
        - secretRef:
            name: r2-to-pg-secret

Environment Variables

Variabel Default Wajib Keterangan
DB_HOST 127.0.0.1 — Host PostgreSQL target
DB_PORT 5432 — Port PostgreSQL target
DB_USER postgres ✅ Username PostgreSQL
DB_PASSWORD — ✅ Password PostgreSQL
DB_NAME — ✅ Nama database target
DB_ADMIN_DB postgres — Database untuk admin ops (drop/create)
R2_ACCOUNT_ID — ✅ Cloudflare Account ID
R2_ACCESS_KEY_ID — ✅ R2 API Access Key ID
R2_SECRET_ACCESS_KEY — ✅ R2 API Secret Access Key
R2_BUCKET — ✅ Nama bucket R2
R2_PREFIX pg-backups — Subfolder di dalam bucket
R2_OBJECT — — File spesifik (kosong = auto-select terbaru)
CLEAN_BEFORE_RESTORE true — Drop/recreate DB sebelum restore
CREATE_DB_IF_NOT_EXISTS true — Buat DB jika belum ada (mode append)
POST_RESTORE_ANALYZE false — Jalankan VACUUM ANALYZE setelah restore
DB_CONNECT_TIMEOUT 30 — Timeout koneksi (detik)

Build dengan Versi PostgreSQL Spesifik

# PostgreSQL 16
docker build --build-arg PG_MAJOR=16 -t r2-to-pg:pg16 ./r2-to-pg

# PostgreSQL 17
docker build --build-arg PG_MAJOR=17 -t r2-to-pg:pg17 ./r2-to-pg

# PostgreSQL 18 (default)
docker build -t r2-to-pg:pg18 ./r2-to-pg

Performance & Disk Usage

Streaming pipeline — tidak ada file temporary di disk:

R2 object → rclone cat stdout → gunzip stdin → psql stdin → PostgreSQL
                                          ^
                                          └─ restore langsung
Backup Size (compressed) Bandwidth Estimasi Durasi Disk Usage
300 MB 100 Mbps ~30 detik 0 bytes
1.5 GB 100 Mbps ~2 menit 0 bytes
3 GB 100 Mbps ~4 menit 0 bytes
3 GB 500 Mbps ~50 detik 0 bytes

Troubleshooting

Error: Restore pipeline GAGAL

Cek log error:

kubectl logs -n <namespace> <pod-name>

Kemungkinan penyebab:

  1. File tidak ditemukan di R2 — cek R2_PREFIX dan R2_OBJECT
  2. Koneksi DB gagal — cek DB_HOST, DB_USER, DB_PASSWORD
  3. Permission denied — user tidak punya hak drop/create database

Error: dropdb gagal / createdb gagal

Solusi: Pastikan DB_USER punya hak superuser atau minimal CREATEDB role.

ALTER USER your_user CREATEDB;

Error: pg_terminate_backend gagal

Solusi: Jalankan dari pod dengan hostNetwork: true agar bisa terminate koneksi lokal.

Requirements

Tool Versi Minimum Keterangan
Bash 4.0+ Semua script
PostgreSQL Client 14+ pg_clone.sh, pg-dump-to-r2
Nginx 1.18+ setup-domain-nginx.sh
Certbot Latest setup-domain-nginx.sh
Docker 20.10+ pg-dump-to-r2
rclone Latest pg-dump-to-r2 (sudah include di image)
kubectl 1.20+ k3s-uninstall.sh (untuk multi-node)

License

MIT

About

Preparing Server

Resources

Readme
Activity

Stars

1 star

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages