Mojolicious lets you write plugins for sharing code across controllers, or 
in the case of a mojo lite app, callbacks.

Another solution is to just write plain old perl modules and include them. 
This is the approach I have taken -- sometimes I write functionality in 
Mojolicious plugins, then realize I need it in something unrelated, so I 
end up refactoring to a standard perl module, and include it in my 
mojolicious app. In general, I try to make my controllers extremely lite -- 
check the input parameters, call out to a mojo plugin or perl module to 
accomplish what is asked, and in the controller, return an appropriate 
response.

On Wednesday, September 30, 2015 at 5:05:22 PM UTC-4, Pablo IaCo wrote:
>
> Hi Folks,
>
> I just wanted to share with you something that I'm trying to figure out.
>
> I'm currently building a small App for my own and it's build like follows
> 1) The App itself (with login and stuff)
> 2) A Back-Office (with login and more stuff and creation of information 
> for the main app)
>
> The question that I want to ask is, that currently I've started to build 
> the main application.pl file, with Mojolicious::Lite, with most of the 
> routes and stuff inside of it.
>
> But my question is, how should I approach to develop the back office? I 
> mean, shall I write the whole thing INSIDE the main application.pl or is 
> it better to create a sepparated application just to handle the back office.
>
> My concern with the second approach is, how to handle those packages that 
> are common to each part? 
>
> Thanks in advance and I'm just doing my first steps into a bigger 
> mojolicious app, so that's why I created this post
> Regards
> Pablo
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.

Reply via email to