Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
OK, given a Vue SPA project with vue-router in it's own directory, say /front and a Laravel project in it's own directory, say /back
I understand how Vue can route to login.vue and register.vue and say, products.vue and how they can axios to the /routes/api.php router.
But, they seem so separate and independent. We want Nova available to our developers and admin folks and a given subset of Nova available to customer team administrators. With Nova installed on the /back, it won't be available via the Vue router in the /front, so... Nova is more important to us than the SPA, so I guess I have to ditch the SPA idea......true?
Seems if you use nova matched with laravel why not an SPA. Just me personally, I don't like SPA's.
I do however use some pages like an spa, like an accounting app I did, updates, add new, etc is all done via a single page view with ajax. Lately I went from jquery to fetch js, but axios will be similar.
Just some thoughts on it.
But if I use http://myvueapp.com/login -- vue router will let me log in.
But if I use http://myvueapp.com/nova -- I will 404 because Nova is not installed here, it's over on the backend !?!
Do I understand this correctly?
@gymdone I don’t understand the question? Nova is an SPA itself. You can have a Nova-based “back end” and a separate SPA for your front-end.
Right, but how do my front-end users access Nova? Can they?
Does this mean that I would have to use Nova thru an axios /api/ call from my SPA and write my own UX/UI ?
@gymdone No. You install Nova normally, and you build your “front-end” SPA outside of that. Then for any requests to /admin or whatever, you show the Nova UI. Anything else, send to your front-end SPA.
Do the front and backend have to be developed and run from the same directory?
Please or to participate in this conversation.