Hello Stefan, we had a thread recently about health checks and possible warmup techniques on the mailing list:
http://mail-archives.apache.org/mod_mbox/tapestry-users/202111.mbox/%3c92ee40fb-cb4c-4a6d-8257-b8215a136...@gmail.com%3e Dmitry shared some awesome code to warmup without needing to call pages manually, see http://mail-archives.apache.org/mod_mbox/tapestry-users/202111.mbox/%3cCA+v6cT9C4XmkSmp=2nfs_vobw30qwgvzurbaprefwww_do6...@mail.gmail.com%3e Doing Resource-minification at build-/deploy-time is a whole other can of worms... The first thing that comes to mind is a Gradle task preparing the assets as needed and Tapestry to load them directly on startup and fill it caches. Both functionalities don't exist (yet). Hope this helps as a starting point. Cheers, Ben On Thu, Dec 23, 2021 at 2:43 PM Stefan Starke <stefan.sta...@cloudflight.io> wrote: > Hello, > > I am currently looking into the topic of minimizing resources like JS, CSS > ahead of time and not before they are requested for the first time. > > I already know that the resource minimizations are cached on a per-locale > base inside JavaScriptStackAssemblerImpl. > > Unfortunately I can not find a way on how to minimize all resources before > a user first requests them. > > My current approach would is to call a Tapestry page that loops over all > javascript resources and therefore triggers the minimization > Something like > > @Inject > > private JavaScriptStackSource javaScriptStackSource; > > > @Inject > > private JavaScriptStackPathConstructor javaScriptStackPathConstructor; > > > /* > ***************************************************************************************************************** > > * Event Handlers > > */ > > > public void minimizeJS() > > { > > for (String stackName : javaScriptStackSource.getStackNames()) > > { > > > > javaScriptStackPathConstructor.constructPathsForJavaScriptStack(stackName); > > } > > > } > > But I do not really like this approach as it implies that somehow I have > to open this URL to make the minimization ahead of time - and even worse I > would need to do this on every machine in a clustered setup. > > So basically I am looking for a way to minimize the resources together > with starting the server or even at build time if possible. > > Thanks for hints and advices! > Stefan >
