DEV Community

Discussion on: Simplify Expo releases with Standard Version

Collapse
gregfenton profile image
gregfenton

This is an awesome write up, and great tool! Thank you.

I am planning on releasing different instances of my app per customer (each customer is a company with multiple users - each company gets its own backend "stack").

So I have different app.config.js per customer. When I do a build, upload and/or publish, I specify the --config (e.g. expo build:ios --config customer1/app.config.js --release-channel customer1).

If I have dozens of customers & customer-configs, thoughts on how to go about keeping these all balanced? Would I simply add more entries to bumpFiles per customer, thus they all get "bumped" at the same time? (My goal is to keep all customers running essentially the same version - each just get their own splash screen/icon/app-name & API keys to the backend stack).

Collapse
gregfenton profile image
gregfenton

I guess one approach would be to use JS code in .versionrc.js so that it dynamically adds each of the customer configurations to the bumpFiles rather than being required to manually add them to the config. If all my customer configs are in a standard location like ./app-configs/<CUSTOMERNAME>/app.config.js, then I could easily do this dynamically....

Collapse
gregfenton profile image
gregfenton

Hopefully this helps someone besides myself. Any and all feedback welcomed on the gist page:

gist.github.com/gregfenton/b81ec01...