Replies: 1 comment 1 reply
-
I do this, and I have a separate frontend directory for all of the vue code.
I then build it and serve it out of the public directory as static assets.
…On Wed, Dec 28, 2022 at 7:00 PM Alexander Povolotsky < ***@***.***> wrote:
Hello
I'm working on a project with complex Vue-based interface, and I see that
Vite and Mojolicious has quite different views on directory structure.
MAYBE I'll just split a project into independent front and back; I'm still
not sure. However, my current view is something like "Mojolicious handles
routes like / /login /logout /api/* and all Vite-generated are just static".
Can anyone share their experience, if any?
—
Reply to this email directly, view it on GitHub
<#2020>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFURPKSXKHVYDGVJAM26QNTWPRW2BANCNFSM6AAAAAATLNHY7A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello
I'm working on a project with complex Vue-based interface, and I see that Vite and Mojolicious has quite different views on directory structure.
MAYBE I'll just split a project into independent front and back; I'm still not sure. However, my current view is something like "Mojolicious handles routes like / /login /logout /api/* and all Vite-generated are just static".
Can anyone share their experience, if any?
Beta Was this translation helpful? Give feedback.
All reactions