Level 61
Depends what you need from those models. There is no reason why not to keep Nova with the rest of your app.
Oct 7, 2020
3
Level 1
Running Nova on a different server?
I'd like to run Nova on a separate server, where we have a lot of other backend stuff running.
My initial thought would be to deploy a copy of the production application there, then install Nova on top of it. Of course, that introduces issues with versioning, as I would want to keep the customized Nova stuff under version control. I'm thinking that maybe git subtrees might be helpful there - not sure.
Another approach I was thinking of was to mount the main application's model folder (and whatever else I needed) via a network mount.
And yet another method might be to create a private composer package with the models in it, and require that on the Nova install.
Anyone have any thoughts on this? Thanks in advance!
Level 1
Actually, there are a variety of reasons why someone wouldn't want to keep Nova on the same server(s) as their primary application. Separation of concerns, security, backend vs frontend, firewalls/VPNs, and so on.
Eventually, I think we'll go the route of making the Laravel models a private composer package which can be deployed with the app, as well as other things such as Nova as needed. But for now, a remote mount via sshfs with uid/gid mapping seems to be working pretty well.
Cheers.
Level 61
Yeah, there is a bunch of theoretical reasons, but Nova is probably secure as Laravel and will not bring any performance penalties.
Maybe you can follow up later on when you implement private composer package just to let us know how it went :)
Please or to participate in this conversation.