-
Notifications
You must be signed in to change notification settings - Fork 0
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
Deploy issue #7
Comments
Looking into this. It seems like the error is I haven't been able to test on Azure. Only Heroku and it works fine there. I'm an an American Expat living in the Netherlands and it is literally impossible for me to register with Azure (they don't support Dutch banks and I don't have access to my American cell phone number). |
Found some other people having an issue with commands like this on Windows Going to try and npm start script of |
I was able to obtain an Azure account with the help of someone back in the 🇺🇸 I know Azure didn't like the I did a test removing lwip from I've contacted Azure support via Twitter. |
Yikes. Might need to check in the node_modules folder? 😢 |
Checking in node_modules made the deploy work but the server crashes. Doing more research
Sounds like I need to build node_modules on a Windows machine? That kind of confuses me because isn't that what Azure is? A Windows machine? |
@aarongustafson This Azure deployment issue has been addressed by switching from Ready for another test. ps: Unfortunately there are still Azure/Edge related issues #5 |
The TL;DR is
So it runs nows. The deployment doesn't break. But unless there is some way to configure Azure to support larger URLs, the hosting environment does not fully support the app. If you color every cell you won't be able to refresh, save, share, export the art-board in any browser. When hosted in other environments such as Heroku the web app works fine with lengthly URLs with the exception that Edge does not support them #5. |
🎉 Fixed the Azure breaking on large URLs issues in de72a0d That was a scary one 👻 |
Added https redirect for Azure in 0ee3ea4 This makes sure HTTP/2 and service workers are a go 🚀 |
@aarongustafson I've tagged a release that is ready for another Azure deployment test with a summary of what was wrong and fixed https://github.com/jpdevries/makeanico/releases/tag/1.0.1-pl |
The text was updated successfully, but these errors were encountered: