An update on this - wro4j maven plugin is most certainly not the way to go
for any kind of a complex project.
It is highly restrictive when matching source files to be processed and
selecting destinations for the processed files.
You will only be happy with this solution if:
- your stylesheet
Agreed Dimitris - upon build is indeed best!
There shouldn't be any inconsistencies provided I make sure both
tapestry-webresources and wro4j are using the same less4j version.
I imagine this will be a very standard pattern so I will aim to share the
working wro4j maven plugin configuration I end
I thing your best solution is what you described.
Compile all less to css on building.
On Tue, Oct 25, 2016 at 4:36 PM, Peter Hvass
wrote:
> Hello all,
>
> Sorry for the late response on this one!
>
> About the warmup page - thanks! I am using this now - it bypasses the
> issues I was facing wi
Hello all,
Sorry for the late response on this one!
About the warmup page - thanks! I am using this now - it bypasses the
issues I was facing with AWS ELB's health checks but still means a *very*
slow deployment time.
I had posted a similar issue from an old work address some time ago - look
for
My own solution was rotation of two DigitalOcean instances using floating
IP (you can do the same with AWS, Docker, etc.) whenever I do a deployment.
My project doesn't have heavy traffic (in that case, I'd consider some
LB-oriented solution, like HAProxy).
Everything, including startup and warm-u
## Page Preloading
It is now possible to pre-load pages at system startup time by making
contributions
to the new PagePreloader service. Pages can be pre-loaded only in
development, only in production,
never, or always.
Quote from 5.4 release notes,Not sure if it will generate the js files at
th
Hey,
I'm struggling with the same problem. I didn't took some time to address it
yet. I think that I've already sent an email on this mailing-list to ask
how could I compile less files at startup and not on demand but no one has
answered it.
I'd be glad to have a solution for that.
Cheers,
Charl
Hi Peter,
The simplest option is a create an empty page that just includes all
important CSS-es and JavaScripts and configure that page as a health check
URL in load balancer.
E.g.
Warmup.java:
@Import(stack = {"core"}, stylesheet = {"my.less"})
public class Warmup {
}
Warmup.tml
And /warmup
Hello all,
The solution is kind of obvious here though I just wanted to feel around
for any alternatives.
I'm deploying a small web application to a Tomcat 8 server handled by
Amazon Web Service's Elastic Beanstalk service - load balancers etc. etc.
This is quite a busy site - so we'll typically
