Runtime variables with Vue CLI

Docker and Vue.js

When building an distributable version of a project, it should be relatively easy to swap out some variables at runtime. The benefit of this is that you can build the code once and then deploy it across your stack without the need to rebuild. There’s nothing more frustrating than building for test and then having to rebuild for production – it technically means you’re playing a guessing game as to whether what worked and was signed off, will actually work next time around! Vue CLI doesn’t cope with this concept very well. Recently, we have been using nuxt.js and there has been an introduction of runtimeConfig as a concept in their nuxt.config.js file. This is a new release as of v2.13 and works very well. There were workarounds before, but this is the next level of easy environment swapping. To […]

Kubernetes for multiple projects

Working with multiple projects at the same time using docker and kubernetes can get painful. Needing to remember contexts, configurations and the way that you interact with those can start to weigh down a local development process. Enter kubernetes namespaces Kubernetes namespaces allow you to separate a context out into multiple namespaces that all act like their own context. This is intended from the documentation to help segregate a kubernetes cluster based on environment (dev, staging, prod etc…) but it is also useful for local contexts. Check your current context is set to either docker-desktop or minikube (whichever you’re using) and create a new namespace: kubectl create namespace {project-name}. You can then list your config to identify your local context and user details with kubectl config view then from this create a new context that is tied to your local context […]