git clone <url-from-advanced-config>
Open the Dev Pop UI:
minikube service -n section-shared developer-pop
Click on the Operations tab.
Enter the git commands you see here inside the repository you cloned down in step #1. Replace “www.site.com” with your domain which is visible in the section.io portal. (note : it won’t actually break anything if you leave it as “site”).
Once you have added the git remote you can push to the Dev PoP by running:
git push developer-pop
If you get this message
Pulling required proxy images, please try again shortly, that means that your machine does not have the proxy images locally and has begun downloading them. Your terminal will look as though it has exited the process and nothing is happening, but the downloads are going on behind the scenes. Try
git push developer-pop every few minutes until the downloads are complete and the push goes through. The length of this process will depend entirely on the speed of your internet connection.
Now that your configurations are running on the Dev Pop, you will need to configure your egress settings (origin server details) to tell the Dev Pop where to pass the HTTP request to. To do this you will use the Dev Pop UI’s Services tab where you will find information about the repository you just pushed up. A page refresh might be needed.
The easiest way to do this is to connect your Dev PoP to your section.io Aperture account and import these configurations.
To do this :
If you have an account in the section.io management console you can link your Developer PoP to your account.
See How to Connect Developer PoP to Aperture for more information.
In the Operations column of the table, there will be a button for you to “Configure” that service. Do this if you do not have a section.io account. It will bring up a modal asking for the following information:
Now, you’re all set. Let’s see your new Developer PoP in action..