Login

u/echoreset

r/commandline r/coolify r/SEO r/CLI r/bigseo
▲ 1 r/SEO

What are ex-ContentKing users monitoring with these days?

Genuine question for anyone who used ContentKing before Conductor absorbed it.

I never got the chance. By the time I went looking for real time monitoring of noindex and canonical changes, it already only existed inside the Conductor enterprise platform, priced for a different universe than mine.

So I worked through the usual suspects instead. Scheduled crawls in Sitebulb or Screaming Frog catch things eventually, but "eventually" can mean days after a release already did the damage. Ahrefs alerts, same story, just slower.

Nothing in the middle. That surprised me.

Either you pay enterprise money or you find out from Search Console when impressions tank. So what did the ex-ContentKing crowd actually land on? A replacement, or did you just change your process around the gap?

reddit.com
u/echoreset — 4 days ago
▲ 12 r/bigseo

Is there anything left between "enterprise suite" and "daily crawl" for catching SEO breakage?

Developer here, I run a handful of my own sites and do backend work for clients. What scares me isn't rankings, it's deploys. A release that ships a noindex meta tag or a staging canonical to production sits there silently until the next crawl notices, and by then Google noticed first.

ContentKing used to be the answer for this as far as I can tell, but since Conductor swallowed it there's no standalone product anymore. Everything I've looked at since falls into one of two buckets: full enterprise suites where monitoring is a feature buried in a platform I don't need, or crawlers that run daily/weekly audits (Sitebulb, Ahrefs alerts, etc), which is way too slow for "a deploy just broke it 4 minutes ago".

What I actually want is dumb and narrow: watch robots meta, robots.txt and canonicals on maybe 20 important pages, recheck right after a deploy, ping me when something drifts.

Nothing I've found does the deploy-triggered part at all.

So, people who were on ContentKing before the acquisition: what did you move to? Or is everyone just eating the risk and finding out from Search Console two weeks later?

reddit.com
u/echoreset — 4 days ago
▲ 3 r/coolify+2 crossposts

CoolDeck - small update

Hello you all,

Small CoolDeck update 👋

I posted here a while ago about the keyboard-first terminal dashboard I built for Coolify and since then, even the Coolify team picked it up and gave it a shoutout on X, which was pretty awesome.

I’ve kept building.

CoolDeck now has:

🕐 Deploy Replay - fleet-wide deploy history, git-log style
🔍 Drift Watch - compare envs across environments, secrets redacted
🚨 Panic Button - one key -> full diagnostic snapshot you can paste into your AI tool

If you run Coolify and spend too much time jumping between services, logs and deployments, I’d genuinely love for you to try it.

GitHub: https://github.com/Resetnak/cooldeck

X: https://x.com/Resetnak

Feedback, issues and feature requests are very welcome.

Thank you for your time!

u/echoreset — 10 days ago
▲ 7 r/coolify

I built CoolDeck - keyboard-first terminal dashboard for Coolify

I built an open-source terminal dashboard for Coolify and am looking for feedback.

I use Coolify regularly, but I wanted a faster way to check deployments, inspect logs, and restart applications without switching away from my terminal.

So I built CoolDeck, a keyboard-first TUI written in Go.

It currently supports:

  • application and deployment status
  • runtime and build logs
  • deploy, restart, start and stop operations
  • multiple Coolify instances
  • combined log tailing across several applications
  • an MCP server for coding agents
  • OS keyring storage for API tokens

You can try the complete UI without connecting a Coolify server or providing a token:

brew install resetnak/tap/cooldeck
cooldeck --demo

GitHub:
https://github.com/Resetnak/cooldeck

I would love feedback from actual Coolify users. What workflow or operation would you want to see added next?

u/echoreset — 15 days ago
▲ 0 r/commandline

Herdr Logbook - Local-first Markdown working memory and activity heatmap for your terminal (Go / Bubble Tea))

Hey everyone,

I built Herdr Logbook an offline, Markdown-first working memory TUI designed for CLI-centric developers.

If you constantly context-switch between git branches, tasks, and terminal panes, keeping track of *what you were doing* and why often ends up scattered across scratchpads or lost entirely.

Herdr Logbook keeps your active task context, developer notes, and architectural decisions right in your terminal as clean, standard `.md` files.

💡 Core Features

  • Instant Capture & Task Switching: Quickly record notes, decisions (ADRs), and TODOs tied to your current project or branch.
  • 4-Week Activity Heatmap (`s`): Visualizes your captured notes and daily streaks (similar to GitHub's contribution graph, but for your internal notes).
  • Automated Standup Roll-up (`y`): Summarizes your recent activity into a clean standup report and copies it to your clipboard.
  • Cross-Project Search: Fast local search over all your notes (`/`).
  • External Editor Hand-off: Opens full note editing in your configured `$EDITOR` (nvim, vim, micro, etc.).

🔒 Philosophy & Design Choices

  • 100% Local & Offline: Plain Markdown on your disk. No cloud, no AI, no telemetry, no SQLite database lock-in.
  • Built with Go & Bubble Tea: Responsive TUI designed to run smoothly alongside your multiplexer (tmux / Herdr).
  • Future-Proof: All data lives in standard `.md` files that you can grep, commit to Git, or read 20 years from now.

GitHub Repository: https://github.com/Resetnak/herdr-logbook

I'd love to hear your feedback, suggestions, or ideas for improvements!

u/echoreset — 20 days ago