-
Notifications
You must be signed in to change notification settings - Fork 71.7k
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
some azure tweaks #215
some azure tweaks #215
Conversation
When deployed on MS azure, the available git commit used to deploy the software is available in the SCM_COMMIT_ID environment variable. We encourage all hosting providers to provide some similar facility to avoid spawning spurious processes. Thanks to @shanselman for reminders and pointers to the fix.
Forcing SSL for Azure Node Debugging Support for Azure Correct Git Attributes Node web.config for Azure, and removed it from gitignore
Enabling Websockets if they are on. Need to confirm if they need to be turned on manually.
Counter-intuitively this needs to be FALSE so IIS can let go of websockets and node can take over.
detect deployed git HEAD in azure
Forcing SSL for Azure PLUS adding WebSockets support
👍 |
On my Digital Ocean server I have NGINX proxying to Node and needed to add a some settings to the config to get sockets to work. Before I did that there was a little bit of a lag waiting on failover This is what I added to my location block:
We should test this with Heroku too, I'll try later today or tonight if no one beats me too it |
Working on Heroku with no changes, think this will be ok for everyone |
@jasoncalabrese Yes, that's an Nginx detail. Socket.io simply falls back in ordinary situations. Glad it works. |
Thanks to @shanselman, we now have several tweaks to improve Azure experience.