{"repo":"gavinr-maps/experience-builder-devops-example","free":true,"listed":false,"github":"https://github.com/gavinr-maps/experience-builder-devops-example","clone":"git clone https://github.com/gavinr-maps/experience-builder-devops-example.git","description":"Use Experience Builder within a devops workflow to automatically build the app on commit.","language":"TypeScript","stars":30,"topics":["arcgis-experience-builder","experience-builder","devops","github-actions"],"license":null,"category":"deployment-docker-iac","readme_excerpt":"ArcGIS Experience Builder Devops Example Use Experience Builder within a devops workflow to automatically build the app on commit. How it works 1. First it downloads the Experience Builder developer edition zip file using curl . 1. Then it unzips Experience Builder, does the NPM installs, copies the app directory into “server/public/apps/0”, copies the custom widgets. 1. Then it runs app-download.js (new in Experience Builder v1.6), which generates the export (deployable) zip. 1. Finally, it takes the deployable zip, unzips it, and publishes it The built app is deployed to GitHub Pages: https://gavinr-maps.github.io/experience-builder-devops-example/ More information on how the GitHub Action script generates the Experience Builder app export can be found here. This deployment strategy is not recommended for production apps, because the user may need to clear their browser cache in order to see web app changes. A workaround to required browser cache clearing is to add these steps to your CI pipline (these steps are not covered in this repository's demo code).","default_branch":null,"files":null,"tree":[],"storefront":"/r/gavinr-maps","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/gavinr-maps/experience-builder-devops-example/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}