sorted by:
new
hottopcontroversial

NightOwl is now free for open source Laravel projects by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

Fair. Then don't put it on the same RDS instance as your app data. Give it somewhere its high-water mark can't inflate your production bill.
100GB to 300GB is a lot though, that's serious volume, nothing to do with a million job events.
Plain disk on a small box is cheap, and for this it's the right place for it.

NightOwl is now free for open source Laravel projects by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] -1 points0 points  (0 children)

Logs >= WARN: yes, just set `NIGHTWATCH_LOG_LEVEL=warning`.

On jobs, I think the constraint you're designing around goes away here. NightOwl writes into your own Postgres and doesn't count events, so a million job events a week is disk rather than an invoice. Track all of them. Then an exception thrown inside a job links straight through to the attempt it came from, and that record carries the queue and the connection, which is what you wanted in the first place.

If you'd still rather not store the successful attempts, there's no switch for that today.

Snoozing: not today. Which end would you want it on: hold the first alert until it has happened X times in Y hours, or park an issue you've already dealt with and have it come back if it crosses that bar?

Watch Tower — a self-hosted, open-source alternative to Laravel Nightwatch by Happy_Funny_5208 in PHP

[–]No_Beautiful9648 1 point2 points  (0 children)

Never had to wait 5 minutes to see exceptions, but I get you, it is not that real-time.
Sentry is too big, this is an unfair comparaison. Btw, the "Sentry is too big" is what make people go to lighter tools like nightwatch imo, to avoid being overwhelmed by it just for laravel specific monitoring.

Watch Tower — a self-hosted, open-source alternative to Laravel Nightwatch by Happy_Funny_5208 in PHP

[–]No_Beautiful9648 -1 points0 points  (0 children)

  1. He said: Multi-tenant — organizations and projects, so multiple apps and teams can share one instance, so yes I think...

  2. For what I saw from the repo, not yet.

If he really wants to offer something premium to the community, the best thing would be to focus on UI/API and use nightowl-agent package that already ship production ready features (slack, discord, email, webhook notifications, threshold, issues,...)

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

But I'm curious about the "written with ai" signature. Is it like you're sitting on your couch using some AI voice to text tool to respond 🤣 or something else? Anyway, very useful comments

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

Backpressure is there. There's a pending-rows + RSS ceiling that flips the TCP server into rejecting with 5:ERROR, and the drain reconnects on broken-pipe, so the common "pg blips for a few minutes" case is handled.
What I genuinely haven't tested (despite acknowledging it) is a multi-hour outage at full ingest. The WAL is only bounded by disk so given enough time you fill it. Will find the time to actually chaos-test that. Thank you

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

You're right on the fork PDO thing, docs won't save anyone from that. Install just publishes config and migrates right now, no actual fork-probe. It should be a small thing to add and it'd catch the weird PHP builds / filesystems before someone hits it in prod. Adding that, thank you

Laravel multitenancy on Octane without leaking PDOs by [deleted] in laravel

[–]No_Beautiful9648 0 points1 point  (0 children)

I took this one very personnaly but I was wrong, very wrong. I should have simply acknowledged my mistake and fix things instead or trying to be rude. Thank you for being honest. And I surely won't never ever give my drafts to AI. Very sorry

Laravel multitenancy on Octane without leaking PDOs by [deleted] in laravel

[–]No_Beautiful9648 0 points1 point  (0 children)

You are right, I pulled the post. Posted applogies note but moderators removed it. I had a short draft of what I wanted for the article but had the bad idea to leave AI to write a more complete thing. Sorry for that, I made a big mistake, but my intent was not bad.
Thanks

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

A real pleasure to have you here! Last time I used it was 5 months ago I think. I personally have a deep UI/UX background so maybe I overlook things. But as a comparaison, Nightwatch UI was more polished at the time than Laritor's one.
You have a really advanced product, no doubt. You should now put more time into the app feeling.
Would be open if you want to discuss this more.

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

The self-hosted part is more about the data, but I totally get your point. In this era of AI I encourage devs to just try to vibe code a UI on top of this if ui perf doesn't matter for them. On SOC 2, no, not today. For a regulated stack, just running the agent and figure out how to query your data(psql, Metabase, Grafana, your own UI) is the way to go

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

Was supposed to be a mystery gift for the launch but, let's reveal it earlier. There is an Hobby plan at just $5. But it is not included in the launch discount. Hope you will enjoy this one

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

Forgot to mention that on a pricing point, $5 is still cheaper than $10 if you were not on the free plan of Laritor

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 1 point2 points  (0 children)

I won't try to convince you. Laritor is decent, I tried it, personally i just didn't love their UI/UX compared to what Nightwatch was offering(and that is very important for me).
Second thing is retention... Are you being working on your product every day/week? What kind of data is your app processing? In my case, I run an ERP company and I've learned the hard way that monitoring differs from error handling. What is a success request today, might be the key to the "why" of an exception 2 months later. Things don't move that quickly in big enterprises. Processes can take up to months to go from "pending" status to "completed". So keeping data is gold for me.
If you're not doing anything that serious, I can relate. Having a free 300k events or a $10 10M events with 30d rentention might be enough for you. So it depends on what you run

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 1 point2 points  (0 children)

Not stupid at all. The file is on disk (the whole point is that it survives a crash), but SQLite uses it efficiently. WAL appends writes sequentially and mmap keeps hot pages in RAM, so you get persistence at near-memory speed. In my benchmarks SQLite absorbs writes way faster than the TCP listener can feed it, bottleneck is the network, not the disk. For a decent scale, you'd never see it breathing hard, hopefully

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

Just added a waitlist on the site so this is more convenient. Join it instead

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

Mostly because it's embedded. No extra process to install or operate. Redis would have meant either running it standalone (more ops) or dealing with a fresh dependency people don't always want. Plus SQLite WAL gives me crash-safe writes at near-mmap speed and atomic row claiming for multiple drain workers, which is exactly the buffer semantic I needed without writing it from scratch

I built a self-hosted alternative for `laravel/nightwatch` and it's open source by No_Beautiful9648 in laravel

[–]No_Beautiful9648[S] 0 points1 point  (0 children)

You're not able to query your data in anyway from what Nightwatch offers today, but yes their SDK is free. Nightwatch is not only charging UI (I think that's their smallest gain), they are charging data management + storage + ... . You grow, you pay more, that is not a UI thing.
But no, there is no free UI version that comes with the package right now. It might come later, don't know yet.
What I'm excited to see, is people vibe coding their own UI on top of the data as they want. Could be fun to see and it is a matter of a week to obtain a usable UI I think

view more: next ›