The import is based solely on a boutiques file that must be provided to VIP at import time.
Before, it was edited by the admin on its PC, uploaded on VIP and then given to the importer. There was to mandatory process about where to upload it on VIP and these lead to boutiques files being scattered on several folders, and it was difficult to find the boutiques of a existing application.
Recently, we decided to create a git repository to save all the boutiques files before import to centralized them in a single reference place. So before uploading a boutiques file on VIP, one should push it in the git repo, and admins knows where to look for a specific boutiques file.
The next step would be to base the VIP import on the git repo instead of VIP-stored boutiques to avoid the upload step and to ensure the git repo is the reference.
The import is based solely on a boutiques file that must be provided to VIP at import time. Before, it was edited by the admin on its PC, uploaded on VIP and then given to the importer. There was to mandatory process about where to upload it on VIP and these lead to boutiques files being scattered on several folders, and it was difficult to find the boutiques of a existing application. Recently, we decided to create a git repository to save all the boutiques files before import to centralized them in a single reference place. So before uploading a boutiques file on VIP, one should push it in the git repo, and admins knows where to look for a specific boutiques file. The next step would be to base the VIP import on the git repo instead of VIP-stored boutiques to avoid the upload step and to ensure the git repo is the reference.