We have a team of developers using the ExperienceBuilder developer edition to create a web app. We are using ArcGIS Enterprise. Different developers may work creating widgets and a theme which they will want to share. What is best practice for doing this? We are planning to:
Is this a good approach?
I've also noticed that experiences can be created locally and there doesn't seem to be a way to push them to the portal. Where are these local experiences stored? Is there another folder separate from the "your-extensions" folder where locally created experiences are stored?
I use Docker as a way of seperating my widget code from the Experience Builder framework, this means that I don't have to commit Experience Builder in to the repo, only my widget code. I mostly use Azure DevOps and build my widgets and apps using pipelines.
In order to share how to do that I've put together some blog posts on how to use docker with Experience Builder and also how to build your widgets and optionally also push them straight in to Portal as well. See below.
Experiences are stored in the server\public\apps folder. Using docker you could also optionally store these in a single folder and map them in to docker. Likewise, you could also use the REST API and some python code in a pipeline to push these portal if you needed to as well. Note, you need Enterprise 11 to host custom widgets.
There is also an approach suggested under the FAQs here as well, if you scroll towards the bottom of the page.
Hope that helps.
I am currently going through the same process to include a team of developers to update app/experience configurations and custom widgets.
I have just setup a couple of BitBucket repos for app configs and custom widgets using information at this FAQ
We are going through and testing the process right now, learning as we go. I have found that even though we are logged into Portal as administrators we can't edit an app/experience as a user other than the owner, so we are having to edit the info.json file for the app to change the ownership as required. I am currently chasing down a better way of overcoming this issue, I tried this suggestion but it does not work. Apparently, there is no ability to perform shared updates, but may come in a later version.