While working on a specific code base, it might be required to deploy the code into a branch in studio besides main for test purpose. Unfortunately, playcanvas-sync only supports a single config json file.
Simply saying it might be needed to have profile based config files.
So, Here I modifed the playcanvas-sync command line option so a profile option is optionally available.
Added Option
-p or --profile
Based on the option value, it will select pcconfig-{profile}.json
Once the config file for each profile is set, you can simple use it by running a different npm command.
While working on a specific code base, it might be required to deploy the code into a branch in studio besides main for test purpose. Unfortunately, playcanvas-sync only supports a single config json file. Simply saying it might be needed to have profile based config files.
So, Here I modifed the playcanvas-sync command line option so a profile option is optionally available.
Added Option
-p
or--profile
Based on the option value, it will select
pcconfig-{profile}.json
Once the config file for each profile is set, you can simple use it by running a different npm command.