New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Deploy always fails #307

Open
HopperTech opened this Issue Oct 3, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@HopperTech
Copy link

HopperTech commented Oct 3, 2018

Have tried the Azure Deploy several times. Making sure the Resource Group previously created was deleted.

And always receive the error

The resource operation completed with terminal provisioning state 'Failed'.

@patrickebates

This comment has been minimized.

Copy link
Member

patrickebates commented Oct 3, 2018

Some questions while I try to reproduce the issue. How many Directories and how many Subscriptions do you have available within the deploy screen?

Also, do you have existing resources which you might want to deploy into? If so, I can give some very quick guidance on that option.

@HopperTech

This comment has been minimized.

Copy link
Author

HopperTech commented Oct 3, 2018

@patrickebates

This comment has been minimized.

Copy link
Member

patrickebates commented Oct 3, 2018

I've seen reports of issues with the entire Azure Deploy system if anything other than the Primary directory is used. It's not something isolated to Project Nami.

Regarding deploying to an existing environment, you also have the option of deploying directly to a Web App without first forking to your own repo. Instructions can be found here...
#289

@HopperTech

This comment has been minimized.

Copy link
Author

HopperTech commented Oct 4, 2018

@patrickebates

This comment has been minimized.

Copy link
Member

patrickebates commented Oct 4, 2018

Almost forgot, when doing your own deploy I recommend that you set the following in App Settings

ProjectNami.UTF8 = 1

Do that before you ever begin the PN install.

@HopperTech

This comment has been minimized.

Copy link
Author

HopperTech commented Oct 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment