Perhaps, but AFAIK we generate index page in all supported i18ned languages, so the process is somehow repeated 12 times which makes is slow I believe.
LZ On Fri, Mar 3, 2017 at 5:11 PM, Ewoud Kohl van Wijngaarden <[email protected]> wrote: > On Fri, Mar 03, 2017 at 04:34:49PM +0100, Lukas Zapletal wrote: >> the rake apipie:cache:index command which we do both in build phase >> and after RPM package installation is slow as hell. What is the reason >> for that? Can't we redesign this to completely avoid need of >> generating this kind of index? For example the page could be >> JavaScript based, plugins would simply drop some metadata files and JS >> would parse them hiding/showing appropriate sections on the index >> page. This should not be too hard, but it will increase user >> experience with installing and updating which we need to improve for >> sure. > > Isn't the cache also used by apipie client bindings (which are used by > tools like hammer)? > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
