export KUBE_EDITOR='code --wait'
Running k edit ... will open up the yaml using Visual Studio Code.
| # Initialize the cluster | |
| sudo kubeadm init --pod-network-cidr=10.244.0.0/16 | |
| # Set up local kubeconfig | |
| mkdir -p $HOME/.kube | |
| sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config | |
| sudo chown $(id -u):$(id -g) $HOME/.kube/config |
| # Get the Docker gpg key | |
| curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - | |
| # Add the Docker repository | |
| sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ | |
| $(lsb_release -cs) \ | |
| stable" | |
| # Get the Kubernetes gpg key | |
| curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add - |
| Previously this gist had a series of files showing a working setup, but, | |
| @burkeholland found a much easier way and demonstrates it here: | |
| https://github.com/burkeholland/nuxt-appservice-windows | |
| Essentially, you'll: | |
| 1. add a .deployment file to instruct kudu to run `npm install` for you, | |
| 2. leverage npm tasks' `postinstall` hook in package.json to trigger the full nuxt build, | |
| 3. add a server.js file in the root that `require`s the default server\index.js file that a nuxt app will already have | |
| Step 3 will be noticed by kudu, which will: |