Can we remove the Azure vendor-lock?

[enlightenedpie]

"The CodePush Server requires Azure Blob Storage to operate."

"CodePush Server is designed to run as Azure App Service"

I understand that this was developed at Microsoft, therefore a strong tie to Azure is par for the course. However, many dev teams (like mine) would love to use the new standalone CodePush but we are in other cloud infras; AWS in my case. It would be a monumental task to convince our tech leadership and devops team to spin up an account with Azure just to run this.

Is there a way we can remove the vendor lock by providing our own binary storage and service runners? I'm just asking the question for now, but if it's currently not possible and you're open to PRs I'd be happy to dig through the code and provide a patch to provide external providers.

Thx!

[lucen-ms]

Please feel free to fork the repository and add whatever functionality you need. We do not accept feature contributions though.

[nmengual]

@enlightenedpie I'm testing to use Redis and S3 instead of Azure services, maybe it can be useful as a base. https://github.com/nmengual/code-push-server

[Dylan-yoon-mp]

@enlightenedpie I'm testing to use Redis and S3 instead of Azure services, maybe it can be useful as a base. https://github.com/nmengual/code-push-server

@nmengual When do you think the testing will be completed?

[htdcx]

You can also try other components: code-push-server-go

[Erwan-DATIN]

Hello everyone,

I guess I'm not alone, any update would be welcomed.
appcenter shutting down deadline coming so fast I'm not sure I expect that much.

"Expo update" could be an alternative to codepush on the paper.
But it looks like "expo SDK" and "Expo Go app" are too much linked :

• Expo go update in Apple Store means you have to update your react-native project with matching expo SDK....