Note: If you don’t have an Aperture account and want to use the devpop to simply test reverse proxies, feel free to skip this section.
In the upper right hand corner of the devpop UI, there is a Connect to Aperture button. When clicking this it will redirect you to Aperture and prompt you to login and authorize the devpop. If you are successful then the Connect to Aperture button will be replaced with a blinking blue icon followed by your email address. »
Although Minikube functions functions best when pointed at an origin server with a publicly available IP address, it is possible to connect DevPop to a local development server. The source of complexity here is dealing with the network bridge between the host machine and the Minikube virtual machine. The following is a set of directions for implementing this using virtual box and a local server running on port 90, but the necessary configuration may vary if you have an alternative setup. »
The Developer PoP is a still in beta and will occasionally have hiccups. This section details some common issues and how to deal with them.
Network connectivity and computer sleep Often if you put your computer to sleep with Minikube running, it will break Minikube’s network adaptor, and you will get 503 errors without a clear cause when you resume operation. This will also prevent you from downloading proxy images as a part of a git push. »
It is possible your Developer PoP IP address may change.
If you see a failure on git push with your Developer PoP, try these steps:
Ensure Minikube is running: minikube status. Obtain the current IP address of Minikube: minikube ip. Substitute the IP address into the following command to update the git remote in your Developer PoP git remote set-url developer-pop http://192.168.99.100:30090/application-name.git. »