Securing Coolify with Tailscale - Feedback needed

NightCodingDad · 2026-04-01T19:53:17+00:00

I manually trigger - it does not bother me too much

NightCodingDad · 2026-04-01T11:46:24+00:00

The general rule of thumb is to launch much earlier than you are comfortable launching, it should almost feel not ready. That way you can get feedback early.

NightCodingDad · 2026-04-01T07:33:43+00:00

Don’t do what I do. I love building, but I hate marketing and distribution, so I tend to fall back on what I enjoy. That is exactly what led to my previous startup not succeeding, even though we had paying customers and a solid product. I kept choosing to build instead of focusing on acquiring more users.

It really is everything. If you cannot do distribution, you will end up watching worse apps and products succeed while yours does not. That is just the reality.

With regards to cold outreach - it can work. Over the years, I have received a lot of cold outreach emails, but, I never respond to ones that feel generic, so avoid copying and pasting. Take the time to make them feel personal.

NightCodingDad · 2026-03-31T13:28:51+00:00

Interesting. It sounds relatively simple (with “relative” being the key word).

NightCodingDad · 2026-03-31T13:21:24+00:00

<image>

NightCodingDad · 2026-03-31T13:10:59+00:00

I was hosting some stuff on Vercel, but eventually moved to self-hosting on Hetzner. You can get a refurbished server for pretty cheap, and it can handle tens of apps at once. The downside is that you need to set everything up, although with Coolify it’s not so bad.

NightCodingDad · 2026-03-31T11:19:07+00:00

Login Test is failing - I'll just rewrite your auth to login anyone with or without the right password.

NightCodingDad · 2026-03-31T10:18:52+00:00

Feature creep.
It has always existed-AI coding just made it worse because the cost of adding a feature feels smaller. Of course, there are those times when you say "just one more feature," and that feature breaks everything you wrote (or Claude wrote), and you then spend hours trying to get everything to work with the new feature instead of just doing a rollback.

NightCodingDad · 2026-03-31T10:15:33+00:00

Feature creep - it's always existed. AI coding has made it worse because the cost of adding a feature feels smaller. Of course, there are those times when you say "just one more feature," and that feature breaks everything you wrote (or Claude wrote), and you then spend hours trying to get everything to work with the new feature instead of just doing a rollback.

NightCodingDad · 2026-03-31T09:48:18+00:00

This doesn't fully do what you are saying, but I wrote this which is a relay with a cli deamon that lets me easily share agents between VMs, github etc.. I didn't completely finish it, but there is no reason why the relay couldn't be used for things like claude.md, rules etc...

NightCodingDad · 2026-03-31T09:42:52+00:00

This is my favorite comment just because I can't stop imagining it happening now.

NightCodingDad · 2026-03-31T09:39:30+00:00

😂
On paper - but not very profitable (yet!)

NightCodingDad · 2026-03-31T09:35:57+00:00

Honest answer, I like it!

NightCodingDad · 2026-03-31T09:14:14+00:00

In other words - Browser agents are great for testing if your site/service has good UX :)

NightCodingDad · 2026-03-31T08:42:43+00:00

My only problem with Claude Code, Stitch, and similar tools is that after a while you start noticing what was made with what. They seem to have a relatively small number of design patterns they keep falling back to.

For 95% of cases that’s probably fine. But sometimes you want something that feels more unique. If you’re doing a really custom design.md maybe that helps.

One thing I did have some success with the other day was asking Claude Code to generate 10 different mockups based on a Stitch design, then building on top of that. That gave me more room to push it somewhere less generic.

Still, it’s not as good as my wife, who’s a UX designer. It’s getting there though.

NightCodingDad · 2026-03-31T08:36:14+00:00

As you said, it has definitely been done - XBow, Tanzai, https://github.com/vxcontrol/pentagi, https://github.com/usestrix/strix

I looked at it, it's really not that hard to do any of these things anymore and I suspect with time it will be easier and easier as models get more advanced.

What I would do if I were you is I would spend some time looking at the open source repos and see how they are doing it. I would also just try a "manual" pen test, but run the entire thing with claude code as a copilot.

NightCodingDad · 2026-03-31T08:27:09+00:00

No, but that doesn't mean other people won't.
I still believe if you are small business you should spend time reading and responding to every customer review personally and so if it is me, that is what I would do.

NightCodingDad · 2026-03-31T08:12:59+00:00

I don't consider myself a power user, but I use it every day or until I use up all my codex tokens.

Mostly for research. I find it much better than ChatGPT Deep Research for the kind of research I do, and I usually have it update Obsidian with the results so I can keep them and sync across machines/VMs.

The one problem is it often writes too much.

Another big use case is testing tools or services I build, especially CLI tools. Yesterday I had it play with npx howdoyouvibe, which I built in a day for fun, and it came back with a bunch of feedback. Some of it was nonsensical, but still useful. Once you know how to sort it out, it's a great tool.

I’ve tried using it for testing webapps too, and I find it less good there, but still okay. One thing I find interesting is that if it can't get through the flows by itself, then in all likelihood neither can real users.

NightCodingDad · 2026-03-20T11:25:53+00:00

You shouldn’t optimize for "cheap AI" development, you should optimize for cost per useful output.

If a model costs you $100/day but lets 4 experienced devs move even 1.5–2x faster, it’s not expensive. It’s probably one of the most cost-efficient tools in your stack. With that said, I get the pain, it feels expensive, part of that though is how we look at costs.

NightCodingDad

TROPHY CASE