-
Notifications
You must be signed in to change notification settings - Fork 79
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 install scripts to dotnetcli account #558
Comments
Completely agree. |
To me this means
These things all require access, yes? My team does not currently - we may need help to get these things done on the short term. |
Recommendation for the install script location:
Which would end up being:
|
That sounds perfect.
|
|
Thanks @rbhanda! I verified that
are available. What resources are being served with the new url, and where are they located? Thinking about what changes to the internal pipelines we'll need to start looking at. |
Could you create a new repo MD file that describes the intended production deployment, covering:
|
All of that content currently lives at https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script (which we should update with the new urls once they are fully-prepped). |
It is hard to see the trees among the forest in that document. I think we need a terse doc that makes it very clear what our intent is. Also, we don't need to document the website location in docs, but we need to here. |
Do you want me to start this doc @baronfel? |
We need to deploy the install scripts so that they are accessible via our CDN.
After recent experiences, we've realized that our website should not be part of our high availability story for installers (via the install script). The CDN is already necessarily part of that. We should limit moving parts as much as possible.
/cc @mmitche
The text was updated successfully, but these errors were encountered: