Replies: 5 comments 4 replies
-
|
I use quasar for the frontend of all my projects (personal + work) with
mojo in the back. Highly recommended, both are progressive (in a non
political way, lol) and thus quite pleasant to build + learn with.
I have mojo serve all the static files, you just need to set them up in the
right directories.
Though I don't quite see exactly what you're asking. What problems are you
forseeing?
…On Mon, May 30, 2022, 22:50 mvharlan ***@***.***> wrote:
Hi,
I like Mojolicious because it's SBOM contains only ONE entry! I also like
quasar/vue because it's neat and easy to use. But it's SBOM has some 1000++
entries.
So I want to do sensitive stuff within perl/mojo and use npm/quasar for
the UI stuff. The npm server should forward all REST calls to mojo and
handle js/css/html/media/... itself.
My questions are:
- Is this a good idea?
- Is there a better solution?
- Should mojo serve all the npm/webpack stuff or is nodejs good enough
for that?
- Are there any examples for my architecture?
Best regards,
Magnus
—
Reply to this email directly, view it on GitHub
<#1943>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFURPKVMKQIJC6WBQJSLZMTVMULYJANCNFSM5XLOI47A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
After starting my first vue project within a active project I asked git to commit a change in my active project. It complained about some 20000 new files in the source tree. That really scared me like hell, because nobody can control all this code and js code is not known for it's quality. Coming from a high security background this is really s nightmare. That's the reason I would like to separate huge npm dependency trees from the really sensitive stuff using crypto, dbs, auth, etc... |
Beta Was this translation helpful? Give feedback.
-
|
Do you have a useful link how to integrate a quasar app into mojo ? |
Beta Was this translation helpful? Give feedback.
-
|
Well, you don't have to build your frontend on the same box where sensitive
stuff is happening. Nor does it have to be in the same repo as your backend.
It compiles ultimately to static files that only run on the client (not
including SSR, but that could also be served on a different box).
…On Mon, May 30, 2022, 23:10 mvharlan ***@***.***> wrote:
After starting my first vue project within a active project I asked git to
commit a change in my active project. It complained about some 20000 new
files in the source tree. That really scared me like hell, because nobody
can control all this code and js code is not known for it's quality. Coming
from a high security background this is really s nightmare. That's the
reason I would like to separate huge npm dependency trees from the really
sensitive stuff using crypto, dbs, auth, etc...
—
Reply to this email directly, view it on GitHub
<#1943 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFURPKV62FDLEGN6NB4QIOLVMUOCJANCNFSM5XLOI47A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
That's exactly my plan. |
Beta Was this translation helpful? Give feedback.
-
|
Also, you should add node_modules to your gitignore
…On Mon, May 30, 2022, 23:12 Veesh Goldman ***@***.***> wrote:
Well, you don't have to build your frontend on the same box where
sensitive stuff is happening. Nor does it have to be in the same repo as
your backend.
It compiles ultimately to static files that only run on the client (not
including SSR, but that could also be served on a different box).
On Mon, May 30, 2022, 23:10 mvharlan ***@***.***> wrote:
> After starting my first vue project within a active project I asked git
> to commit a change in my active project. It complained about some 20000 new
> files in the source tree. That really scared me like hell, because nobody
> can control all this code and js code is not known for it's quality. Coming
> from a high security background this is really s nightmare. That's the
> reason I would like to separate huge npm dependency trees from the really
> sensitive stuff using crypto, dbs, auth, etc...
>
> —
> Reply to this email directly, view it on GitHub
> <#1943 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFURPKV62FDLEGN6NB4QIOLVMUOCJANCNFSM5XLOI47A>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
|
I learned that quite early (-: |
Beta Was this translation helpful? Give feedback.
-
|
Quasar isn't node based (unless you're using SSR).
You use the quasar build command to minify + whatnot your files into a
bunch of static files, which you can serve as static files.
…On Tue, May 31, 2022 at 2:13 PM Franz Skale ***@***.***> wrote:
Do you have a useful link how to integrate a quasar app into mojo ?
Since it's nodjs based, a server is forked to serve the logic.
Would be very helpful, for starters…
Best regards
Franz
—
Reply to this email directly, view it on GitHub
<#1943 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFURPKV5XF74WFQK2EUZ2B3VMXX5DANCNFSM5XLOI47A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Btw. mojo.js now also exists. 😉 |
Beta Was this translation helpful? Give feedback.
-
Hi,
I like Mojolicious because it's SBOM contains only ONE entry! I also like quasar/vue because it's neat and easy to use. But it's SBOM has some 1000++ entries.
So I want to do sensitive stuff within perl/mojo and use npm/quasar for the UI stuff. The npm server should forward all REST calls to mojo and handle js/css/html/media/... itself.
My questions are:
Best regards,
Magnus
Beta Was this translation helpful? Give feedback.
All reactions