config | My dotfiles | Configuration Management library

The next-fire-base-auth config documentation links to the cookies package. Under the cookies example, I found:

If you are using vuetify from vue-cli-plugin-vuetify (vue add vuetify), treeshaking and auto component import is enabled by default, by using vuetify-loader.

If you look into the source code of vue-cli-plugin-vuetify, it only uses vuetify-loader if it is present in your package.json. So removing vuetify-loader from package.json should disable this behavior.

try require('dotenv').config()

You need access throught JSON, there has an option:

Nuxt makes the $config available in two ways: as this.$config on every component instance, and context.$config passed to "special nuxt lifecycle areas like asyncData, fetch, plugins, middleware and nuxtServerInit" (docs).

It looks like you need to access the $config outside a component, so you'll need to retrieve it early in the request cycle. In particular, since you're mutating the Vue.prototype, this feels like a good fit for a plugin in the Nuxt sense, which isn't quite what you've got in your code.

If you put your plugin file in the plugins directory and reference it from the plugins array in nuxt.config.js (see link above for a broader example), you could rewrite it like this to access $config:

Why are you calling client in a command file if you already started a new instance of a client in your root file? try removing client from the top of the code. Hope that works

Not sure but I'm guessing the --key argument only supports prefix. You could use jmespath to work around that:

By default plumber is trying to send a valid JSON response. If that's not what you want, change the serialize to something like text and return an empty string

Starting with 6.4 RC5 (which is the version you run as of this writing and should provide this in your original post):

The collection of thymeleaf user interface template pages are no longer found in the context root of the web application resources. Instead, they are organized and grouped into logical folders for each feature category. For example, the pages that deal with login or logout functionality can now be found inside login or logout directories. The page names themselves remain unchecked. You should always cross-check the template locations with the CAS WAR Overlay and use the tooling provided by the build to locate or fetch the templates from the CAS web application context.

https://apereo.github.io/cas/development/release_notes/RC5.html#thymeleaf-user-interface-pages

Please read the release notes and adjust your setup.

All templates are listed here: https://apereo.github.io/cas/development/ux/User-Interface-Customization-Views.html#templates