Toby

Laravel 12 support has been released in 0.4.11.

Hi @Thomas Thaulow, sorry for the delay! Not dead, just on a bit of a hiatus.

Rather than inserting Waterhole into your existing frontend, you'll need to insert your custom header/footer into Waterhole's frontend. You can do this using the LayoutBefore and LayoutAfter extenders along with some custom CSS.

The tricky thing is that Waterhole has its own design system that makes use of global styles and classes, so you may need to be careful/selective with which CSS you bring in from your own frontend, and possibly make some adaptations. It's possible in the future that I'll look at namespacing Waterhole's CSS to make customisations like this easier.

It's not possible to completely eliminate specific comments from Google's index, but spam comments are hidden by default, which Google's algorithm is probably smart enough to understand. Also, all links within posts/comments have the rel="nofollow ugc" attribute so they are not regarded as trustworthy.

Good point! I'll have to think about the best way to prevent this - probably the listener just needs to be removed from Waterhole and added to the skeleton app.

@Andres Smerkin Thanks for the reminder! I'll push out a release with support for Laravel 12 next week - possibly 0.5 will be ready, but if not, then a 0.4 patch release.

The free trial is the exact same code as the licensed version, there's no throttling or anything of the kind.

Make sure you've followed all of the recommendations in the Deploying Optimization docs.

Other than that, it's a known issue that Waterhole's rendering can be a tad slow, due to the extensible component-based architecture. It's noticeable on the homepage because there are a lot of components rendered for each post in the list. It's definitely something I'd like to improve in the future.

It is very much proportional to CPU speed so on waterhole.dev we use a droplet with a "premium" CPU to make it go a bit faster.

You could also consider reducing the number of posts per page in your config (though understand that's not ideal).

Thanks for the report @Benjamin Gakami, I'll look into this.

Hi @George, thanks for your question! There is no built-in way to do this at the moment (will consider adding a channels page in the future), but for now you'd need to build it yourself. It'd be pretty conventional Laravel stuff, adding a route, controller, and view to retrieve and render a list of Waterhole's Structure models.

You can configure the core JS setup in config/waterhole/system.php under echo_config. Replace it with whatever config you would need to use for Reverb, per the Laravel Broadcasting docs.

Hi @James Pence, this is a current limitation of the Laravel auth integration, to be added in a future release. Your proposed workaround sounds reasonable - let me know how this goes, here to answer any questions if needed.

s9e\TextFormatter is an original project under active development.