Lattis

I am in the process of introducing single page applications to where I work. For development, using node based build tools is much easier for the single page applications. However, the build process for our organization is based upon maven. Our solution started with the maven plugin frontend-maven-plugin. It worked great at first, but then we ran into a situation that I couldn't make work with it.

As stated before, at our organization, we have the older ecosystem which is maven and the newer ecosystem which is node. Our goal was to keep the hacking to a minimum. We did this by putting all of the hacks into a single super node based build file. This is what maven calls and the reason frontend-maven-plugin wasn't sufficient. The super node based build script calls all of the other build scripts by spawning npm run. Try as I might, I could not figure out how to make the spawn work. front-end-maven-plugin downloads npm

	# Alex Ellis 2018
	# Example from: https://blog.alexellis.io/quick-look-at-google-kaniko/

	# Pre-steps:
	# kubectl create secret generic docker-config --from-file $HOME/.docker/config.json

	# Other potential optimizations (suggested by @errordeveloper)
	# - Store "templates" in a permanent volume
	# - Download source via "tar" instead of git clone

	apiVersion: v1
	kind: ReplicationController
	metadata:
	name: kube-registry-v0
	namespace: kube-system
	labels:
	k8s-app: kube-registry
	version: v0
	spec:
	replicas: 1

	import java.io.IOException;

	import javax.servlet.Filter;
	import javax.servlet.FilterChain;
	import javax.servlet.FilterConfig;
	import javax.servlet.ServletException;
	import javax.servlet.ServletRequest;
	import javax.servlet.ServletResponse;
	import javax.servlet.http.HttpServletResponse;