Joe

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?