[0.17 beta] Feature request: add option in quasar.conf for user agent

Since SSR uses a lot of CPU, on one of our servers we render just for a specific user agent like for exaple if the user agent is twitterbot, we use Nginx to make the decision like(the following is Nginx configurations code snippet):

if ($http_user_agent ~* "baiduspider|twitterbot|facebookexternalhit|rogerbot|linkedinbot|embedly|quora link preview|showyoubot|outbrain|pinterest|slackbot|vkShare|W3C_Validator") {
    set $prerender 1;
}

I wish if I can specify in quasar.conf file for which user agent we want to use the SSR but for the others send them the SPA/PWA files as static files without rendering them.

Can you add this feature, please?

[MohammedAl-Mahdawi]

Hi @rstoenescu thank you so much, I understand, I’m going to work on this and will update here when I get any progress in case if anyone faced a similar issue in the future.

[rstoenescu]

When you build for SSR then the distributable code is SSR specific (as it needs to be). You can’t just serve the created “www” folder without it being rendered within a SSR context.

However, you can create two builds (one for SSR, one for SPA/PWA), put them on your server, then mangle with the production server (mentioned earlier - src-ssr/index.js) to distribute the requests accordingly to the User Agent. Make some Google searches on express if it’s too foggy or you don’t know where to begin. As a last resort, if mangling with express doesn’t works, I suggest that you make a deployment script so you don’t have to repeat the same deployment steps “by hand”.

This pretty specific request cannot be managed from a quasar.conf property, unfortunately, so you have to do it yourself in src-ssr/index.js.