GhostBin A lightweight pastebin, built with Go and Redis

Here’s a clean, compelling *Hacker News–style launch post* you can copy/paste. I’ll keep it concise, technical, and aligned with HN norms (no hype, no emojis, no marketing fluff).

---

*Title:* GhostBin — A lightweight pastebin alternative to ix.io, built with Go + Redis

*Text:* Hi HN,

I built *GhostBin*, a lightweight pastebin designed to replace the simplicity and speed that services like ix.io used to offer. ix.io has been down for a long time, and most existing pastebins are either bloated, slow, or not CLI-friendly. I needed something minimal that “just works,” especially for piping logs and command outputs during debugging or writing content. So I made my own.

GhostBin focuses on:

* *Simplicity:* Clean interface and a straightforward API. * *Performance:* Go + Redis for fast reads/writes. * *CLI-first workflow:* `curl` and shell pipelines work out of the box. * *Privacy & control:* Self-hostable with Docker; no vendor lock-in. * *Burn-after-read + expiration:* Useful for ephemeral snippets. * *Optional deletion secret:* Allows secure deletion via API.

Demo: [https://gbin.me](https://gbin.me) Video: [YT Video](https://www.youtube.com/shorts/RINJI_Q5048) Source: [https://github.com/0x30c4/GhostBin](https://github.com/0x30c4/GhostBin) CLI script: [https://raw.githubusercontent.com/0x30c4/GhostBin/main/gbin.sh](https://raw.githubusercontent.com/0x30c4/GhostBin/main/gbin.sh)

### Example Usage

Upload a file:

``` curl -F "f=@file.txt" gbin.me ```

Pipe command output:

``` dmesg | curl -F "f=@-" gbin.me ```

Expiration / read limits / custom URL length:

``` curl -F "f=@file" -F "expire=60" -F "read=1" -F "deepurl=8" gbin.me ```

Secure deletion:

``` curl -F "f=@file" -F "secret=pass" gbin.me curl -XDELETE -F "secret=pass" gbin.me/<id> ```

### Self-hosting

GhostBin ships with a full Docker Compose setup. You can spin up a local or production instance with:

``` make up-dev make up-prod ```

Config is handled via `.env` files, and the Makefile wraps the common workflows.

---

I’d love feedback on:

* security considerations I may have missed * the overall API design * edge cases worth testing * whether people would want syntax highlighting / raw mode / versioning or if that adds unwanted bloat

Thanks! Happy to answer questions.

---

If you want, I can generate a *shorter*, *longer*, or *more casual* version too.