search

aspnet / dnvm

OBSOLETE - see readme
Other
174 stars 61 forks source link

dnvm setup should set DNX_HOME machine-wide on Windows #439

Closed analogrelay closed 8 years ago

analogrelay commented 9 years ago

When we install DNVM on Windows, we should set the DNX_HOME environment variable to the appropriate value (including global install dirs). This should be in the dnvm-setup function, and should run only if elevated.

The MSI should (already?) set the same environment variable so this would only be for scenarios where DNVM is installed via the "copy-pasta" script.

/cc @marcind @BrennanConroy @glennc

marcind commented 9 years ago

Make sure the MSI is available via Web Platform Installer.

analogrelay commented 9 years ago

@danroth27 @DamianEdwards Are there plans to integrate our MSIs into WebPI?

glennc commented 9 years ago

I haven't talked about adding it to WebPI with anyone yet, but it should be possible. I take it you like WebPI and want to use that to install all of our stuff?

@anurse this is just to prep the machine for wherever we may drop DNXs in the future?

marcind commented 9 years ago

@glennc I'm looking for any method that allows me to install dependencies onto a target host in a 'one-liner' declarative, idempotent fashion (i.e. I can automate this). WebPI and Chocolatey fit that bill as I can just choose the product and version and they take care of the rest (including no-op if it's already installed). No need to look up download links, manage MSIs, etc. So if you're going to have an MSI, make sure to add it to those registries.

Though honestly, I've been quite happy with the capabilities of DNVM so far (esp. once the machine-wide install story gets completed).

analogrelay commented 9 years ago

We've also had people ask about PowerShell Package Management/Desired State Configuration support which is compatible with MSIs.

In general, I think a major RC-level thing will be refining our acquisition story so feedback here is welcome :). In this case, dnvm could have (and basically does already) it's own idempotent "machine setup" script so that all you have to do is bring dnvm.ps1 to the box, run setup and maybe update-self to get the true latest (if you didn't directly download the latest) and you should be set.

marcind commented 9 years ago

Since we're talking about covering all the bases here, having this available via apt-get on Ubuntu would also be great :)

DamianEdwards commented 9 years ago

@marcind we're working on that right now. We plan to have the following acquisition experiences ready for RC in November (some may come online earlier):

dougbu commented 9 years ago

Looking at #473, I see we need to revisit the approach for this issue.

The MSI should (already?) set the same environment variable

Is no longer true. Nothing sets $env:DNX_HOME, $env:DNX_GLOBAL_HOME or $env:DNX_USER_HOME. Their use is reserved for overrides since the scripts et cetera know how to calculate correct default values for every user.

That said machine-wide settings may be useful for Windows services or machine-wide installations in non-default locations. Perhaps this option needs a separate dnvm command or off-by-default option for dnvm setup...

analogrelay commented 9 years ago

@dougbu @cesarbs and I chatted and there are some other issues in this. We'll try to resync on this next week (maybe try to track down @davidfowl). A couple things noted:

I think I covered most things, but @dougbu or @cesarbs can expand on this if not :)

cesarblum commented 8 years ago

@anurse Is this still relevant?

analogrelay commented 8 years ago

Nope, not relevant