Re: Mojolicious::Lite and Webperl

This sounds like an XY Problem for me.

Distributing a web application to every user to be capable to run an SQL query means that the access to the SQL-Server is exposed to everybody who looks into the HTML sources.

If you can't install a web application on your companies apache why don't you try to run Mojolicious standalone on another "private" host?

You can put a static page on your apache which redirects to this private server.

Your application doesn't seem to be heavy enough to exclude being run in Mojo's own webserver.

I really like seeing more apps running into webperl but this sounds weird.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

Comment on Re: Mojolicious::Lite and Webperl

Replies are listed 'Best First'.
Re^2: Mojolicious::Lite and Webperl by frazap (Monk) on Apr 11, 2019 at 09:13 UTC
Thanks for commenting LanX We did what you outlined above: run the mojolicous daemon on a virtual server on a Windows pc, and link to the generated search page from the main site. The script is in my my scratchpad, and the interface is a just a form web page. And, yes: using one app that would be run in the browser using WebPerl would have the same problem as distributing an exe that would be run on every interested user'pc: how to prevent users from getting access to the mysql server directly. frazap	[reply]
Re^3: Mojolicious::Lite and Webperl by LanX (Saint) on Apr 11, 2019 at 09:52 UTC
> We did what you outlined above: So your problem is solved now? Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^4: Mojolicious::Lite and Webperl by frazap (Monk) on Apr 11, 2019 at 10:12 UTC
Yes it is... frazap	[reply]


Syntactic Confectionery Delight
	PerlMonks