Can Waterhole be installed as a "drop in" to an existing Laravel installation in the same way that, say, Statamic CMS can be? There doesn't seem to be a mention of this in the docs.
If not, I guess installing it on the same domain alongside an existing installation and tweaking the nginx config would be acceptable, but if I've already got 50K users signed up in my existing Laravel installation for services that Waterhole will not be replacing, what would be the best way to provide a seamless experience so that they're not having to log in again to use Waterhole features?
6 Comments
Hi @Joe,
Yes, this is something that I'm planning to add official support/docs for. For now it's untested and probably fairly limited (eg. there's no way to configure a separate DB connection for Waterhole). But the gist would be:
composer require waterholeforum/coreinto your Laravel projectIn terms of auth integration, there's no solution at the moment but it's also on the roadmap for one of the next couple releases.
Official support with auth would be great. I have a couple existing projects that could benefit from a self hosted community (currently on Circle). Right now, the Oauth flow with Circle works, but isn't optimal.
Do you think you can provide us with an update on this?
I am interested in using this product for my project.
Any update ?
Not to pile-on here, but... I notice the 0.3 release blog mentions support for dropping into an existing project, is that still planned for 0.4? It would be awesome if it were possible to drop waterhole into a fresh laravel spark project!
Sorry all for the lack of recent updates on this! Happy to say that development on the Laravel integration is done and I'm aiming to release 0.4 within the next week or two.