1. Clone application’s git repository
Clone your application’s git repository located in the Advanced Config menu in the Section portal.
git clone <url-from-advanced-config>
2. Add the Dev PoP remote to your repository
- Open the Dev Pop UI:
minikube service -n section-shared developer-pop
- This may take a few minutes if the pods in the cluster are still spinning up. Check the status by running the following:
kubectl get pods -n section-shared --selector=app=webux
The application section.io-Developer-PoP is requesting access to your Section accounts.
Upon approval, your browser will be redirected to the following URL with an access token appended:
http://192.168.99.102:32080/app/aperture-connected.html Allow access?
- Click on the Operations tab.
Add Dev PoP Remote to Local Application Repository
Enter the git commands you see here inside the repository you cloned down in Step 1.
cd www.site.com git remote add developer-pop http://<IP-From-Operations-Tab>:30090/www.site.com.git
Replace www.site.com with your domain which is visible in the Section portal. It won’t actually break anything if you leave it as “site”.
3. Push your configuration files to the Developer PoP
Once you have added the git remote you can push to the Dev PoP by running:
git push developer-pop
git push developer-pop Counting objects: 176, done. Delta compression using up to 4 threads. Compressing objects: 100% (132/132), done. Writing objects: 100% (176/176), 306.64 KiB | 38.33 MiB/s, done. Total 176 (delta 37), reused 176 (delta 37) remote: Resolving deltas: 100% (37/37), done. remote: remote: varnish image not found, pulling from repository remote: modsecurity image not found, pulling from repository remote: Pulling required proxy images, please try again shortly To http://192.168.99.101:30090/www.site.com.git ! [remote rejected] Production -> Production (pre-receive hook declined) error: failed to push some refs to 'http://192.168.99.101:30090/www.site.com.git'
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.
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 and the power of your computer.
➜ bootcamp.section.io git:(Production) git push developer-pop Counting objects: 176, done. Delta compression using up to 4 threads. Compressing objects: 100% (132/132), done. Writing objects: 100% (176/176), 306.64 KiB | 61.33 MiB/s, done. Total 176 (delta 37), reused 176 (delta 37) remote: Resolving deltas: 100% (37/37), done. remote: Validating configuration for proxy varnish... remote: Validating configuration for proxy modsecurity... To http://192.168.99.101:30090/www.site.com.git * [new branch] Production -> Production
4. Configure origin server details
Now that your configurations are running on the Dev Pop, you will need to configure your origin server details to tell the Dev Pop where to pass the HTTP request.
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.
(a) Connect Dev PoP to Aperture
Make sure to connect your Dev PoP to your Aperture account and import the Environment configurations.
- Click on Import under the Operations column in the Services tab.
- Select the Environment you want to test. i.e Production
- Click on Import to finish importing the configurations.
To Import an Application and its Environments you must be invited as a User for that Account. This is done via Aperture: Account > Manage Users > Invite User.
(b) Configure the service manually
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 account. It will bring up a modal asking for the following information:
- Hosted Name: This is the host headers for your application (e.g. www.example.com).
- Origin Address: This is the either a domain name or IP address that points directly to your load balancer or webserver.
- Origin Host Header: This is the host header the egress will use to send upstream (typically it’s the same as your hosted name).
Now, you’re all set. Let’s see your new Developer PoP in action..