DEV Community: Ketut Dana

XtermChat | A Terminal Chat App With a Built-in Server Monitoring Bot

Ketut Dana — Sun, 15 Mar 2026 13:28:24 +0000

A few months ago I got tired of giving my team's conversations to third-party servers. So I built XtermChat — a self-hosted chat system that runs entirely in the terminal.

Since then, it has grown into something I didn't originally plan: a full client-server chat system with a terminal TUI, a web admin panel, and a bot that monitors your VPS and sends alerts directly into your chat rooms.

This post is about what it became.

What XtermChat Is Now

At its core, XtermChat is still simple: a Python Flask server, a SQLite database, and a CLI client. But it now ships with three ways to use it.

1. Terminal TUI — the original interface. Run xtc start:chat @general and you get a full terminal UI with three panels, dual-focus mode, emoji shortcuts, link detection, and clipboard copy.

2. Web Admin Panel — run xtc start:web and open localhost:5000. Full admin panel with dashboard, room management, chat with link previews (OG image, title, description), and bot management.

3. Bot System — run xtc start:bot and a setup wizard walks you through configuring a monitoring bot that runs as a background process on your VPS.

The Bot System

This is the part I'm most excited about. The idea is simple: instead of setting up a separate alerting tool, XtermChat already has rooms and messaging — so why not use that infrastructure for server monitoring too?

$ xtc start:bot

┌──────────────────────────────────────┐
│   XTERMCHAT  ·  BOT SETUP            │
└──────────────────────────────────────┘

▸ SELECT ROOM
  1. @general    OPEN   by KETUT
  2. @alerts     OPEN   by KETUT

▸ Bot name: MONITOR

▸ SELECT BOT TASKS
  1.  Resource Monitor     CPU, RAM, Disk usage
  2.  Process Monitor      Watch if a service dies
  3.  Uptime Watchdog      Ping a URL every N minutes
  4.  Port Checker         Verify ports are open
  5.  SSL Cert Checker     Alert before cert expires
  6.  Log Watcher          Tail a log for keywords
  ...

▸ Select tasks: 1,3

✓ Config saved  (bot_id: 1)
✓ Bot started on server  (PID: 24891)

The bot runs as a background process on the VPS. It reads its config from the database, checks at the configured interval, and sends alerts as normal messages to any room you choose.

An alert looks like this in your chat:

⚠️ RESOURCE ALERT on srv1260384 [15 Mar 2026 08:30:00]
  CPU   85%  (limit 80%)
  RAM   91%  (limit 85%)

Because it's just a message in a room, you can see it from the terminal TUI, the web admin, or any client connected to the server.

The Architecture

The whole thing is two repos.

xtc-server — lives on your VPS:

xtc-server/
├── server.py       Flask app, all API + bot routes
├── db.py           SQLite init (users, rooms, messages, bots)
├── room.py         Room CRUD, bcrypt passwords
├── connection.py   Message save/retrieval
└── bot_runner.py   Bot background process

xtc-client — lives on your machine:

xtc-client/
├── xtc.py          CLI entry point, command dispatcher
├── utils.py        Hardware UUID identity
├── commands/
│   ├── chat.py     Terminal TUI
│   ├── bot.py      Bot setup wizard
│   ├── bot_stop.py Stop/list bots
│   ├── listBots.py List all registered bots
│   └── deleteBot.py Delete bots
└── web/
    ├── app.py      Flask web server (port 5000)
    └── html/       5 admin pages

The client sends a POST /bot/start to the server, which spawns bot_runner.py as a background process. The bot reads its config from the database and starts monitoring. Stop it with xtc stop:bot 1 which sends POST /bot/kill — the server kills the PID and updates the database.

The Web Admin

The web admin surprised me with how useful it turned out. I built it for team members who don't use the terminal, but I ended up using it myself because the chat bubble UI with link previews is genuinely nicer for long conversations.

The chat page fetches Open Graph metadata for any URL shared in a message — image, title, description, favicon. It's cached per session so the same URL isn't fetched twice.

One thing worth noting: the web admin uses a 5-digit PIN you choose at login, while the CLI uses a hardware UUID auto-generated from your machine. Both work with the same server and the same rooms. The difference is that CLI identity is device-bound (if you reinstall your OS, your PIN changes), while web identity is portable.

What I Learned

SQLite is underrated. The entire server state — users, rooms, messages, bot configs — lives in one file. Backup is cp xtc.db backup.db. For a team of 2–50 people on a $5 VPS, it's more than enough.

REST over WebSocket was the right call. Polling every 2 seconds is fine for this use case and dramatically simpler to implement, debug, and extend. The bot just makes HTTP requests too — same pattern everywhere.

Hardware UUID as identity is surprisingly clean. No passwords to remember. Your machine is your identity. The tradeoff is that switching devices requires an admin to reset your entry, but for a small team that's a non-issue.

Try It

Server: github.com/dnysaz/xtc-server
Client: github.com/dnysaz/xtc-client
Docs: xtermchat.vercel.app

Setup takes about 10 minutes. The docs cover everything from server setup to HTTPS to the full bot task reference.

If you run a small team, manage a homelab, or just want your chat data to stay on your own infrastructure — give it a try. And if you find something broken or have a feature idea, issues and pull requests are very welcome.

Built with Python · Runs on a $5 VPS · MIT License

Try XtermChat | Self Hosted Terminal Chat App

Ketut Dana — Sat, 14 Mar 2026 05:16:19 +0000

I got tired of my team's messages living on someone else's server.

Not because I'm paranoid. Just because I could do better. Slack logs everything. Discord has its own rules. Matrix is powerful but setting it up feels like a weekend project. Mattermost is great — if you have an afternoon and enjoy reading YAML.

So I built something simpler.

What is XtermChat?

XtermChat is a self-hosted chat system that runs entirely in the terminal. You deploy the server on your own VPS, your team connects with a CLI client, and that's it. No accounts, no dashboards, no third-party anything.

┌──────────────────────────────────────────────────────────────┐
│                      X T E R M  C H A T                      │
│               For Those Who Speak Terminal.                  │
└──────────────────────────────────────────────────────────────┘

  ▸ COMMANDS
    connect          Connect client to a server
    disconnect       Remove saved server config
    status           Check server connection
    list:rooms       List all available rooms
    create:room      Create a new room
    delete:room      Delete a room permanently
    start:chat       Open interactive chat
    start:web        Open web interface

Why another chat tool?

Fair question. Here's my honest comparison:

	XtermChat	Matrix	Mattermost	Slack
Self-hosted	✅	✅	✅	❌
Open source	✅	✅	⚠️ partial	❌
Setup time	~5 min	~2 hrs	~30 min	instant
RAM usage	~30 MB	~1–2 GB	~300 MB	—
Terminal-first	✅	❌	❌	❌
Your data	✅	✅	✅	❌

The gap I wanted to fill: something that's self-hosted, lightweight, and actually fast to set up — especially for developers who live in the terminal anyway.

The setup is genuinely fast

Server side (your VPS)

git clone https://github.com/dnysaz/xtc-server.git
cd xtc-server
pip install flask flask-cors
sudo ufw allow 8080
python3 server.py start
# [*] Server started in background (PID: 12345)

That's it. No database configuration. No config files to edit. SQLite handles everything automatically on first run.

Client side (your machine)

git clone https://github.com/dnysaz/xtc-client.git
cd xtc-client
make install
xtc connect @your-server-ip:8080

Now you're connected. Create a room and start chatting:

xtc create:room @general
xtc start:chat @general

Total time from zero to chatting: under 10 minutes, including the time it takes to spin up a VPS.

The chat UI

When you run xtc start:chat, you get a full terminal UI — not just a scrolling log. There's a left sidebar showing your identity and connection info, a right sidebar with room details, and a chat area in the middle.

A few things I'm particularly happy with:

Tab to switch modes. Press Tab to move focus from the input box into the chat history. From there you can scroll, select text, and copy it — just like a normal text editor.

Links are clickable. URLs in messages show up with underline formatting. Move your cursor to a link and press Ctrl+L to open it in your browser.

Emoji shortcuts. Type :fire and it converts to 🔥 when you send. Type :e to see all available shortcuts in a floating panel.

  XtermChat-CLI  |  NODE: mac-dana  |  103.45.67.89  |  [ INPUT ]

  ┌─────────────┬──────────────────────────────────┬─────────────┐
  │ ID          │                                  │ CHANNEL     │
  │  KETUT      │  now  You   ❯  hey everyone!     │  #GENERAL   │
  │             │  2m   John  ❯  hello!            │             │
  │ GATEWAY     │  5m   You   ❯  https://github.com│ CREATOR     │
  │  103.45.7   │                                  │  KETUT      │
  └─────────────┴──────────────────────────────────┴─────────────┘
  ✏️  INPUT MODE  │  ENTER: SEND  │  TAB: → CHAT  │  Ctrl+X: EXIT
   Message ❯❯❯ _

How identity works

There's no signup. Your username comes from your system user (whoami), and your identity is tied to your machine's hardware UUID. First time you send a message, you're automatically registered on the server. If someone else tries to use the same username from a different machine, the server rejects it.

This means:

No passwords to remember for your identity
No accounts to create
Your identity is device-bound — which is actually the right behavior for a team tool

Room passwords are hashed with bcrypt. Only the room creator (verified by hardware PIN) can delete a room or wipe its message history.

Web interface included

Not everyone on a team lives in the terminal. So there's also a web UI:

xtc start:web
# URL: http://localhost:5000

Open it in a browser, enter your server IP, a username, and a 5-digit PIN — that's your identity for the web client. It talks to the same server API as the CLI, so everyone sees the same messages regardless of which client they're using.

The stack

Backend: Python + Flask, SQLite3
CLI: Python with prompt_toolkit
Web: Flask serving plain HTML + vanilla JS
Auth: Hardware UUID (CLI) or user-chosen PIN (web)
Protocol: REST API over HTTP or HTTPS

No Docker required. No Postgres. No Redis. No node_modules. The entire server runs on Python with two pip packages.

What's next

A few things I'm thinking about:

End-to-end encryption for messages
File sharing (small files, inline in chat)
Webhook support for notifications from CI/CD pipelines
Federation — connecting multiple servers so teams on different VPS instances can chat

But honestly the current version already does exactly what I need day to day. Sometimes simple is the right call.

Try it

Server: github.com/dnysaz/xtc-server
Client: github.com/dnysaz/xtc-client

This is the documentation : https://xtermchat.vercel.app/

If you're running a small team, managing a homelab, or just want your chat data to stay on your own infrastructure — give it a shot. The setup is fast enough that there's really no reason not to try.

And if you find something broken or have a feature idea, issues and pull requests are very welcome.

Built with Python. Runs on a $5 VPS. Your data stays yours.

I Built a Framework That’s 17x Faster Than Laravel : Meet Kuppa.js

Ketut Dana — Sat, 21 Feb 2026 14:08:24 +0000

Building a web application often feels like a trade-off. You either go with a "batteries-included" framework like Laravel but sacrifice raw performance, or you pick a minimalist tool like Express.js but spend hours wiring up folders, auth, and database connections.

This past weekend, I decided to stop choosing. I built Kuppa.js, an opinionated, high-performance framework built on top of Express.js, specifically optimized for the Supabase ecosystem.

Why Kuppa.js?

The goal was simple: Developer Experience of Laravel + Raw Speed of Node.js.

Express.js is famous for being unopinionated. It’s just a blank canvas. Kuppa.js turns that canvas into a structured environment. It tells you where your migrations go, how your controllers should look, and comes with Supabase Auth baked in by default. It moves Express from a library to a real framework.

The "Brutal" Benchmark: Kuppa vs. Laravel

I didn't want to just claim it’s fast. I ran an Apache Benchmark (ab) with 5,000 requests and a concurrency level of 100 on my local machine.

The Setup:

Laravel: Serving a static home page (No DB, No Auth).
Kuppa.js: Serving a home page with Active Database Session & Auth Check.

The Results:

Metric	Laravel (Static)	Kuppa.js (Auth + DB)
Requests per Second	63.00 #/sec	1,043.53 #/sec
Avg. Latency	1,587 ms	95 ms
Success Rate	100%	100%

Kuppa.js outperformed Laravel by 17x, even while doing the heavy lifting of checking authentication. This is the power of a non-blocking I/O combined with a lightweight, opinionated structure.

Key Features

Opinionated Structure: No more "Where should I put this file?" questions. Standardized Models, Controllers, and Core logic.
Supabase Native: Deep integration for Database and Auth out of the box.
CLI Driven: Manage your database with custom commands like kuppa migrate and kuppa db.
Security First: Database inspections are handled via custom PostgreSQL functions with SECURITY DEFINER to ensure the CLI is powerful but safe.

A Weekend Project Gone Open Source

Kuppa.js started as a "home weekend project" to scratch my own itch. It’s now open source because I believe there's a middle ground for developers who love the Supabase stack but miss the structure of a real framework.

It’s still in its early stages, but the foundation is rock solid.

What's Next? Bridging DX and Hardened Security

The core is ready, but a framework is only as good as its stability. My next focus for Kuppa.js is to maximize the developer experience without compromising on security:

Strict Security Layer: Implementing a standardized validation layer (via Zod/Joi) to ensure every input is sanitized before it even touches the Supabase RPC.
Advanced CLI Generators: Expanding the CLI to not only generate boilerplate but also scaffold secure-by-default controllers and models with built-in error handling.
Enhanced Database Inspection: Improving the kuppa db utility to provide deeper insights into Row Level Security (RLS) policies and PostgreSQL performance bottlenecks.
Automated API Documentation: Auto-generating Swagger/OpenAPI specs directly from your Kuppa routes to make frontend integration seamless.

Check out the project here:

https://github.com/dnysaz/kuppa-app

Start :

npx create-kuppa my-kuppa-app

I’m building Kuppa.js to be the go-to for devs who want Laravel’s productivity with Node.js’s performance. I’d love to hear your thoughts—especially on how you handle security in high-performance environments.

Critiques are welcome. If you see any bottlenecks in how I handle the Supabase RPC or have suggestions on making the security layer even tighter, please let me know. I'm building this to be a production-ready framework, and your feedback is crucial to making that happen.

javascript #nodejs #supabase #webdev #performance

dwrite.me update features custom & simple Rich Text Editor

Ketut Dana — Tue, 10 Feb 2026 07:07:44 +0000

Hello,

dwrite just got a major upgrade! We’ve officially launched our Custom & Simple Rich Text Editor. This update gives you full control over your formatting: Bold, Italic, Underline, Headings (H1-H6), and Block Quotes.

This is quote!

And for the tech savvy, we’ve added Syntax Highlighting for code snippets, like this:

<div> hello world </div>

I’m really excited about this because now you can style your thoughts exactly how you want. This feature is also optional—you can switch to a distraction-free mode by toggling the button at the bottom of the page.

Important Note: The Paste function remains disabled in the regular editor to keep our content handcrafted. :) But... I’ve made an exception for the Code Editor—you can paste your snippets there freely! :D

Another Update: Notifications are live! Whenever someone leaves a comment on your article, you’ll see an alert on your profile.

That’s all for now. Thank you, and have a good day!

Please visit at https://dwrite.me/feed

Let’s Get Back to Real Human Thought with dwrite.me

Ketut Dana — Mon, 09 Feb 2026 03:44:54 +0000

Lately, the internet has started to feel loud, yet incredibly empty. Every time I browse Google, Medium, or news portals, I run into articles that feel "too perfect." The structure is flawless, the grammar is impeccable, but there is absolutely no soul in them.

We all know why. It’s AI.

As a developer, I love technology. But as a human, I’ve started to crave writing that has "scars"—writing that has emotion, rhythm, and is actually born from someone’s messy brain, not a polished prompt.

That’s why I built dwrite.me.

An Internet That’s Too Fast
My frustration is simple: We live in an age where everything is expected to be instant. Need a 2,000-word article? One click. Need an opinion? Ask a chatbot.

But here’s the problem: If everyone is using AI to write, why should we bother reading each other at all? We aren't exchanging thoughts anymore; we are just swapping machine-processed data. Our way of thinking is becoming lazy. We no longer value the "friction" of struggling to find the right words. Yet, that struggle is exactly where our humanity lives.

The Broken Bridge Between Us
I used to read blogs to feel like I was having a conversation with the author. I could feel their anxiety, their excitement, or even their confusion.

Now? That bridge feels broken. AI writing is sterile. There are no surprises, no bold opinions, no "wrong" takes. Everything is safe. I’m worried that if we keep going down this path, we’ll forget how to connect honestly through words. We’re becoming content consumers instead of thought appreciators.

dwrite.me: Back to Basics
I built dwrite.me with a very simple concept. In fact, it might be too simple by today's standards.

No AI, Just Friction:
I want people to feel the effort of typing again. I want there to be a "clash" between the mind and the keyboard.

Pure Minimalism:
No clutter, no distractions. No Copy Paste. It’s just you and your message.

Handcrafted:
Every word typed here is a conscious choice made by a human being.

I don’t expect this platform to compete with the giants like Medium or Substack. Not at all. dwrite.me is just a small space for those who still believe that human thought with all its flaws is infinitely more valuable than a text generated by a thousand servers in a matter of seconds.

If you also feel like the internet is getting drowned in automated "noise," maybe we’re on the same frequency.

Check it out at dwrite.me. Let’s start thinking again, one slow word at a time.

https://dwrite.me

Open for collaboration. Let’s build this together if you have the same vision.

w3site.id cara baru untuk hosting situs statis secara gratis lengkap dengan AI site builder

Ketut Dana — Tue, 03 Feb 2026 07:57:02 +0000

Halo! Kenalin nih, w3site.id, cara paling sat-set buat kamu yang mau hosting situs statis tanpa ribet. Gak cuma urusan hosting, kamu juga bisa dapet subdomain .w3site.id secara gratis tis tis! Cocok banget buat kamu yang butuh rumah digital buat portofolio atau proyek iseng tapi mau kelihatan tetep pro tanpa harus boncos di awal.

Yang bikin makin gokil, kita punya fitur AI Site Builder yang beneran jenius. Kamu tinggal ketik konsep situs impianmu, dan boom! AI kita bakal bikinin situs statis instan cuma dalam hitungan detik. Gak cuma itu, fiturnya komplit banget mulai dari bikin landing page simpel, biolink ala-ala selebgram, shortlink, sampai SEO article generator. Bahkan, buat kamu yang lagi mau mulai bisnis, ada fitur cek SWOT juga biar strategi kamu makin matang dan anti-gagal!

Buat kamu kaum mendang-mending, tenang aja karena ada Paket Gratis yang oke punya. Kamu bisa langsung dapet slot buat 2 situs dengan SSD storage 256MB yang pastinya kenceng. Ini kesempatan emas buat kamu yang mau pamer karya atau sekadar coba-coba bikin sticky notes online sendiri. Yuk, buruan join di w3site.id dan bikin jejak digitalmu jadi lebih keren sekarang juga!

Kunjungi : https://w3site.id

I Built Clip10: A Real-time Clipboard with "Terminal" Commands

Ketut Dana — Mon, 29 Dec 2025 09:12:53 +0000

*Hi everyone! *

I want to share a project I’ve been working on called Clip10. It’s basically a web-based clipboard where you can drop links, notes, or images, and they sync across all your devices in real-time.

But there’s a twist: everything disappears in 10 minutes unless you tell it not to!

Why I built this?

Sometimes I just need to move a link or a photo from my laptop to my phone quickly. I don't want to email myself or use a bloated messaging app. I wanted something "frictionless"—just open, type, and done.

The Cool Part: Commands in the Editor

Instead of clicking many buttons, I built a Command-Line Interface (CLI) directly inside the text editor. You just type a command and hit Enter.

Type these commands in the editor and press Enter to execute:

Command	Action	Description
`:help`	Open UI Menu	Displays the English command reference modal.
`:show-qr`	Share Link	Generates a QR Code modal for the current session.
`:image`	Share Image	Upload images to the content.
`:save`	Download	Exports the current text as a `.txt` file.
`:clear`	Wipe Data	Deletes all text in the editor and syncs with DB.
`:stop-time`	Freeze Timer	Activates ∞ INFINITY mode (Saved to DB).
`:start-time`	Resume Timer	Restores the 10-minute countdown logic.

How I made it? (The Tech Stack)

I kept the stack simple but powerful:

Frontend: Plain HTML and Tailwind CSS (I love Dark Mode!).
Database & Real-time: Supabase. This is the MVP here. It handles the live syncing perfectly. When I type on my PC, the text appears on my phone instantly.
Link Engine: I wrote a custom Regex to detect URLs. If you type google.com, it automatically turns blue and clickable.
Previews: I used the Microlink API so that links show a nice visual card (like on Discord or Slack).

Features at a glance:

Smart Detection: It knows if you're typing a link or just text.
Ephemeral by Default: Great for privacy. Your data vanishes after 10 minutes.
Local Export: You can save your notes as a .txt file using the :save command.
QR Handoff: No need to type long URLs on your mobile browser.

What I learned

Building this project taught me a lot about handling real-time data and how to build a "command processor" in JavaScript. Sometimes, the best UI is actually just a simple text box that can do everything.

What do you think? Is a 10-minute timer too short, or just right for privacy? I'd love to hear your feedback!

Check out the documentation in my README for more details.

https://github.com/dnysaz/clip10

https://clip10.vercel.app

Mengembangkan Bahasa Pemrograman Baru, Apakah Masih Relevan Saat Ini?

Ketut Dana — Thu, 16 Oct 2025 02:27:19 +0000

Setiap kali seseorang bilang ingin membuat bahasa pemrograman baru, reaksi pertama yang sering muncul adalah tawa kecil atau skeptisisme:

“Untuk apa? Sudah ada Python, Rust, Go, JavaScript,PHP, Java, C , C++ dan ratusan lainnya.”

Dan saya paham kenapa begitu.

Kita hidup di era di mana hampir semua kebutuhan pengembangan sudah punya alatnya. Ada framework untuk setiap gaya berpikir, ada library untuk setiap masalah, bahkan ada AI yang bisa menulis kode lebih cepat dari manusia. Jadi, muncul pertanyaan yang wajar: kenapa masih ada orang yang merasa perlu membuat bahasa pemrograman baru?

Keresahan Itu Datang Dari “Rasa Tidak Cukup”

Setiap developer pasti pernah merasakan momen di mana mereka tidak puas dengan cara sebuah bahasa memaksa mereka berpikir. Bukan karena bahasanya jelek, tapi karena cara berbahasa itu tidak lagi terasa alami.

Kita terbiasa menyesuaikan diri dengan sintaks, aturan, dan paradigma yang sudah ditentukan. Tapi lama-kelamaan, muncul rasa ingin membalikkan arah: Bagaimana kalau justru bahasa yang menyesuaikan diri dengan cara kita berpikir?

Di situlah keresahan itu tumbuh. Bukan soal ingin menciptakan sesuatu yang “lebih baik dari semua bahasa lain”, tapi lebih kepada ingin menemukan cara baru untuk berpikir dan menulis logika.

Apakah Dunia Masih Butuh Bahasa Baru?

Kalau kita bicara efisiensi murni mungkin tidak. Tapi kalau bicara ekspresi, pendidikan, budaya berpikir, dan inovasi, jawabannya: ya, sangat mungkin.

Bahasa pemrograman bukan sekadar alat menulis instruksi untuk mesin. Ia juga cara manusia menstrukturkan logika, mengekspresikan ide, dan berkomunikasi dengan sistem. Bahasa baru sering lahir dari ketidakpuasan terhadap batas-batas yang ada — dan justru dari sanalah teknologi berkembang.

Tidak semua bahasa baru harus menggantikan yang lama. Beberapa mungkin hanya menjadi eksperimen singkat, tapi eksperimen itulah yang mendorong batas pemikiran komunitas developer.

Dampaknya Tidak Selalu Besar — Tapi Bisa Bermakna

Kita sering menilai “relevansi” dari seberapa banyak orang yang memakainya. Padahal, terkadang, dampak sejati dari sebuah bahasa bukan pada jumlah penggunanya, tapi pada cara berpikir baru yang ia tanamkan.

Setiap bahasa membawa filosofi tersendiri:

Ada yang fokus pada kesederhanaan.
Ada yang ingin ekstrem dalam efisiensi.
Ada yang mencoba mendekatkan manusia dan mesin melalui bentuk ekspresi baru.

Dan di sinilah poin pentingnya: membuat bahasa baru bukan hanya soal menulis compiler, tapi soal menciptakan ruang ide baru bagi cara manusia memahami teknologi.

Bagaimana Saya Memulainya

Awalnya bukan karena ambisi besar, tapi karena rasa penasaran:

“Bagaimana kalau bahasa ini bisa ditulis dengan cara yang lebih manusiawi?”

“Bagaimana kalau sintaksnya bisa berbicara dalam cara berpikir yang berbeda?”

Dari pertanyaan sederhana itu, saya mulai mencatat ide, menulis contoh kecil, bereksperimen dengan parser, dan melihat bagaimana satu baris kode bisa punya makna yang lebih dekat dengan niat penulisnya.

Itu bukan perjalanan cepat. Membuat bahasa bahkan sekadar prototipe adalah proses panjang antara logika, bahasa manusia, dan kesabaran. Tapi setiap kali satu konsep berhasil dijalankan, ada rasa kepuasan yang tidak tergantikan:rasa bahwa saya sedang mencoba menciptakan “cara berpikir baru”.

Penutup

Apakah dunia masih butuh bahasa pemrograman baru? Mungkin tidak untuk efisiensi, tapi ya untuk evolusi berpikir.

Selama masih ada orang yang merasa bahwa mesin bisa lebih memahami manusia, selama masih ada yang ingin menulis kode dengan rasa ingin tahu, maka selalu ada ruang bagi bahasa baru untuk lahir. Bukan untuk menggantikan, tapi untuk menambah warna dalam cara kita memahami logika dan teknologi.

VinotesApp: A Simple and Practical Online Sticky Notes

Ketut Dana — Tue, 12 Aug 2025 10:07:39 +0000

Have you ever needed to jot something down quickly without the hassle of heavy apps or carrying around sticky note papers? That’s where VinotesApp comes in as the perfect solution.

What is VinotesApp?

VinotesApp is an online note-taking site that works just like sticky notes. The difference is, while sticky notes are physical papers you stick on your desk or laptop, VinotesApp is the digital and online version. So you can access your notes anytime, anywhere, without worrying about losing them.

Key Features of VinotesApp

Easy login with Google accountNo long sign-ups needed — just log in with your Google account.
Create new notes with one clickClick the “+” button to create a new note, then click outside the note area to save it automatically.
Mark important notesNotes marked as important will always appear in front so you don’t miss them.
Customize note colorsMake your notes more fun and organized by choosing your favorite colors.

The Technology Behind VinotesApp

VinotesApp is built with lightweight and efficient technology:

Laravel 11 as the backend framework
Socialite for Google authentication
SQLite as a simple, fast, and easy-to-maintain database

A Simple Project with Practical Purpose

VinotesApp is a simple project created to solve a common need for quick and easy online note-taking. It’s not packed with dozens of complex features, but focuses on doing one thing well: helping you keep your notes accessible and organized without fuss.

Recognized by Laravel News

VinotesApp was also featured by Laravel News, a popular community and news site for Laravel developers. You can check out their LinkedIn post about VinotesApp here:

https://www.linkedin.com/posts/laravel-news_the-simplest-online-sticky-notes-app-activity-7331018475634659329-1iI4/

Why Choose VinotesApp?

Because VinotesApp focuses on simplicity and ease of use. No installation, no complicated setup. All your notes are securely stored online and accessible wherever you are.

Interested? Try it now at vinotesapp.com and experience the ease of online note-taking!

Why I Stopped Chasing the "Cool Stack" Everyone’s Using

Ketut Dana — Wed, 06 Aug 2025 13:42:19 +0000

And why that's been the best decision I’ve made for my productivity.

A few years ago, I remember feeling this pressure.

Everyone was talking about the "right" stack to use.

You must use React.
You have to build with Docker.
If you’re still using PHP? “Yikes, bro.”

At first, I tried to keep up.I thought maybe I was falling behind. Maybe I was doing it wrong.

But the more I tried to force myself to follow the “industry standard,” the more I realized:

The industry doesn't know what I’m building.

So I stopped.

What I Actually Needed

I work on small web apps. Sometimes for myself. Sometimes for clients.Most of the time, I don’t need Kubernetes. Or TypeScript. Or an entire CI/CD pipeline just to post a blog.

What I do need is:

A simple backend that runs
A form that works
A layout I can style quickly
Something I can ship fast and maintain alone

That’s it. I don’t need a spaceship. I need a scooter.

I Even Built My Own Framework

Yeah. Instead of chasing tools I didn’t enjoy, I built something I actually like using.

I called it VeltoPHP. It’s not big. It’s not fancy.It’s just something that makes sense for me.

Why?

Laravel was powerful, but too heavy for what I wanted.
I didn’t want to depend on updates or breaking changes from packages I don’t use.
I wanted to enjoy building again.

Is it better than Laravel? Nope.Is it better for me? 100%.

A Great Stack Isn’t the One Everyone Uses — It’s the One You Understand

I’ve seen people throw shade at PHP, at jQuery, at whatever’s not trendy.I’ve also seen indie developers build solid, profitable apps with those exact tools.

And that’s when it hit me:

Most of the time, “best practices” just mean “what works best for me.”

If it works, it works.If you understand it, and you can move fast with it — that’s your stack.

Stop Telling People What Stack They Have to Use

We all build different things.

Some of us work in big teams.Some of us are solo developers.Some are launching startups.Some are building projects after work with limited time and energy.

Why should we all use the same tools?

Why should we shame someone for choosing something they are comfortable with?

Idealism Is Cool — As Long As It’s Not Fanaticism

Look, I love seeing developers who care deeply about clean architecture, patterns, and performance.But I also think there’s a line between sharing knowledge and forcing opinions.

Not everyone has the same goals.Not everyone has the same constraints.

The moment we forget that, we stop building community — and start building echo chambers.

What Actually Matters

At the end of the day, I don’t want to be remembered for the stack I used.I want to be remembered for the things I built — and the problems I solved.

The best tech choice is the one that lets you ship, learn, and grow.

No stack will magically make you a better developer.But choosing the right stack for your needs? That’s wisdom.

Final Thoughts

I don’t care if you're using PHP, Go, Ruby, or Vanilla JS.What matters is: Are you building something that matters to you?

If the answer is yes — you’re doing great.

And if anyone tells you otherwise, just remember:

You don’t need their permission to build your way.

What About You?

Have you ever felt pressured to use a certain tech stack?Or are you already walking your own path?

Drop a comment — I’d love to hear your story.

Hack Shared Hosting: Use Composer 2 + PHP 8.3 Without Root Access!

Ketut Dana — Thu, 31 Jul 2025 07:42:34 +0000

Because sometimes, all you need is a modern dev environment — and your hosting provider says no 😤

The Shared Hosting Problem

If you're on a typical shared hosting (especially with cPanel):

❌ Composer is stuck at version 1.x

❌ CLI PHP version is ancient (sometimes PHP 5.6 🤯)

❌ You can't install tools globally or change system settings

But you need Composer 2 and PHP 8.3+ to run modern frameworks like Laravel, Symfony, or even custom ones.

What You’ll Achieve

Without root, you’ll get:

✅ PHP 8.3 CLI — not just for .htaccess, but for terminal too
✅ Composer 2.8+ installed globally (in your user space)
✅ A persistent setup (survives logout or server reboot)

Step 1: Create a Local ~/bin Folder


mkdir -p ~/bin

This is where we'll install your personal Composer binary.

Step 2: Install Composer 2 Locally


cd ~/bin
php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php composer-setup.php --install-dir=~/bin --filename=composer
php -r "unlink('composer-setup.php');"

✅ This will install composer into ~/bin/composer.

Make sure you're using the correct PHP binary (we’ll handle that next).

Step 3: Add ~/bin to Your Shell PATH

Edit ~/.bashrc and add this line:


export PATH="$HOME/bin:$PATH"

Or via terminal:


echo 'export PATH="$HOME/bin:$PATH"' >> ~/.bashrc

This makes your local composer override any global one.

Step 4: Ensure .bashrc Loads on Login

If you're using ~/.bash_profile, make sure it sources .bashrc:


echo 'source ~/.bashrc' >> ~/.bash_profile

Step 5: Use the PHP Version You Want (e.g., PHP 8.3)

Most shared hostings offer multiple PHP versions stored in /opt/alt/, such as:


/opt/alt/php83/usr/bin/php

To use PHP 8.3:


alias php='/opt/alt/php83/usr/bin/php'

To make this permanent:


echo "alias php='/opt/alt/php83/usr/bin/php'" >> ~/.bashrc

Now every php command will use PHP 8.3.

Final Step: Reload Shell


source ~/.bashrc

Or logout and SSH back in.

Test Your Setup


which php
php -v

which composer
composer -V

Expected output:


~/bin/composer
Composer version 2.8.x
PHP version 8.3.x (/opt/alt/php83/usr/bin/php)

Why This Works

Shared hosting doesn’t restrict what you do inside your own home directory

We installed Composer locally and adjusted your shell environment
We aliased php to point to the correct version
No root required, nothing breaks the server
You just created your own dev environment inside a locked-down system .

Final Words

You just outsmarted your shared hosting provider.
PHP 8.3 and Composer 2 — on your terms, no root, no VPS, no extra cost.

If this helped you, share it with fellow devs.
Because we all deserve a real dev environment, even on the cheapest hosting plans.

Happy Coding!

image credit : Designed by fullvector / Freepik

Saya Membuat VeltoPHP Karena Laravel Terlalu Luar Biasa untuk Saya yang Suka Membuat Sesuatu yang Sederhana

Ketut Dana — Thu, 24 Jul 2025 10:28:21 +0000

Halo! 👋

Nama saya KetutDana, dan saya ingin berbagi cerita pribadi — tentang bagaimana dan kenapa saya akhirnya menciptakan sebuah framework PHP bernama VeltoPHP.

Awal Mula: Dari HTML ke PHP

Saya mulai belajar programming pada tahun 2017. Waktu itu, saya bekerja bersama sepupu saya, yang juga memperkenalkan saya pada dunia koding.

Proyek pertama saya sangat sederhana — hanya sebuah website statis berbasis HTML dan CSS. Tanpa backend. Tanpa framework. Bukan karena saya tidak ingin menggunakannya, tapi karena saya bahkan tidak tahu mereka itu apa.

Saya bukan lulusan IT. Tidak punya latar belakang pendidikan formal di bidang ini. Hanya ada satu hal yang saya bawa: rasa ingin tahu dan minat belajar yang tinggi. Itu yang menjadi bahan bakar saya sejak hari pertama.

Mengenal PHP dan Belajar Backend

Sepupu saya memperkenalkan saya ke bahasa pemrograman pertama saya: PHP.

Kenapa PHP? Karena dia bisa PHP. 😄

Awalnya saya bingung — kenapa kita perlu backend? Apa itu database? Apa itu CRUD?

Semua itu asing.

Tapi waktu berjalan, dan sedikit demi sedikit saya mulai paham. (Bukan langsung mahir, hanya paham konsep dasarnya.)

Saya ingat betul, proyek PHP pertama saya adalah membuat clone WhatsApp menggunakan Bootstrap dan PHP murni. Kodenya sangat mentah, tidak aman, bahkan rentan terhadap SQL Injection — tapi itu adalah titik awal penting bagi saya.

Itu adalah awal dari semuanya.

Ketemu Laravel — dan Jatuh Cinta

Setelah cukup bermain-main dengan PHP murni, saya menemukan sebuah framework bernama Laravel. Waktu itu Laravel 5 sedang populer. Saya mencobanya dan... wow!

Saya sangat kagum. Laravel terasa elegan, lengkap, dan sangat nyaman digunakan. Saya mulai membuat berbagai proyek pribadi dengan Laravel — tidak untuk dipublikasikan, hanya untuk belajar dan bersenang-senang.

Tahun 2021, saya menggunakan Laravel 8 untuk hampir semua proyek saya.

Tapi Lama-lama Laravel Terlalu Besar untuk Saya

Semakin hari, Laravel semakin berkembang. Laravel 9, 10, 11, 12 — semuanya luar biasa. Tapi di sisi lain, saya mulai merasa "kecil".

Saya ini programmer hobi. Saya suka ngoding untuk mengisi waktu, bukan untuk mengelola sistem enterprise berskala besar. Saya ingin bikin proyek-proyek kecil, ringan, dan sederhana.

Laravel jadi terasa terlalu kompleks untuk kebutuhan saya.

Seolah saya hanya seekor semut yang mencoba naik gajah.

Lahirnya VeltoPHP

Awal tahun 2025, saya mulai memikirkan blueprint framework sendiri:

Sebuah framework yang tetap enak digunakan, memiliki gaya penulisan seindah Laravel, tapi jauh lebih ringan dan fokus untuk hal-hal sederhana.

Lahirlah VeltoPHP, sebuah micro-framework yang awalnya mengusung konsep RVC (Route-View-Controller) — versi super ringan dari MVC, tanpa database, tanpa ORM, tanpa embel-embel.

Tujuannya sederhana:

Untuk membuat website statis dan aplikasi kecil dengan cepat dan nyaman.

Lalu Hadirlah Axion

Tapi kemudian saya sadar:

VeltoPHP terlalu sederhana jika tidak ada dukungan backend yang proper. Kalau tidak bisa konek ke database dan tidak bisa menangani login, buat apa ada framework?

Akhirnya saya membuat modul tambahan bernama Axion — semacam plugin auth & model — agar VeltoPHP bisa berubah menjadi framework fullstack jika dibutuhkan.

Tapi ternyata... itu tidak cukup. Banyak error muncul jika pengguna tidak menggunakan Axion dengan benar. Arsitektur awalnya terlalu rapuh.

Saran yang Mengubah Arah: HMVC

Dari komunitas Dev.to, saya dapat masukan berharga:

"Kenapa tidak pakai arsitektur modular, seperti HMVC?"

Saran itu membuka pikiran saya. Saya pelajari konsep HMVC dan menyadari bahwa:

Modul bisa lebih terisolasi
Bug tidak menyebar ke seluruh sistem
Pengembangan jadi lebih fleksibel

Akhirnya, lahirlah VeltoPHP V.2, dengan arsitektur HMVC, sistem middleware, dan built-in auth module (Axion) yang kini menjadi bagian inti dari VeltoPHP, bukan ekstensi terpisah.

Status Saat Ini

VeltoPHP V.2 masih dalam tahap pengembangan aktif.

Belum saya sarankan untuk digunakan di production. Tapi untuk pembelajaran, prototyping, atau eksperimen backend ringan — VeltoPHP sudah cukup menyenangkan digunakan.

Harapan Saya

Saya tahu saya bukan siapa-siapa. Saya bukan developer besar.

Tapi saya punya mimpi kecil:

Saya ingin VeltoPHP bisa bermanfaat — setidaknya untuk orang-orang seperti saya.

Orang yang suka ngoding, bukan untuk membangun startup 1 miliar dolar, tapi hanya untuk membangun sesuatu yang sederhana, belajar sesuatu yang baru, dan bersenang-senang dengan kode.

Kalau kamu tertarik ikut mengembangkan VeltoPHP, saya akan sangat senang.

Framework ini open source dan selalu terbuka untuk kontribusi dari siapa pun.

Salam,

KetutDana

Creator of VeltoPHP

➡️ github.com/veltophp