I have not played with Windows since 2012, so my information is guesswork (disclaimer). In a SaaS environment, I am not sure if we pulled it down from a shared drive (like S: mapped to a server \\someserver\goodies). Some of the deploy or change configuration was through bubble gum and scripts using batch, powershell, rake, and psake, partially to build versioned code and assets (for rollback capability and cache busting). Powershell has a remote execution capability that helped in some of this.
For access, obviously, you need an account that has administrator access. For a vagrant system, the vagrant account should have this capability as part of building a vagrant compatible vagrant system. For deployments, there may be a way to push them over using windows remoting, or with cygwin sshd, winsshd, or use a deploy tool like Octopus Deploy (https://octopusdeploy.com/). Alternatively, you can package up the code + assets into a package like NuGet, MSI, 7Zip, or Chocolately. Then use a change configuration agent (Puppet, Chef, CFEngine) pull it down. On the topic of IIS application pool (and workers) this is something you can configure in the GUI, which will modify an xml file (found in %*WinDir*%\System32\Inetsrv\Config) that can be copied off and reused. If is error prone to modify that directly, but sometimes is required for advanced configurations. There's a IIS admin command line tool that does a decent job of this, which we used. At the time, the powershell wrappers were not all that intuitive or robust (win2008r2). There's also a cert utility that is good for installed certs for the web services into the store so that can be accessible (and referenced) in the IIS's xml configuration. On Friday, July 24, 2015 at 2:03:30 PM UTC-7, Jamie Jackson wrote: > > As has been mentioned before > <https://groups.google.com/d/topic/vagrant-up/mk4MfEayVGg/discussion>, > using standard VirtualBox shares from a Windows guest to a Windows host is > problematic when developing for IIS. (The permissions don't work out.) > > I've seen recommendations in a few places to manually configure an SMB > share on the host, and to use that from the guest; however, I don't know > how to approach the permissions. > > - For which user should the host share be created? (Domain user? > Machine user?) > - On the guest, how does IIS access the share (UNC? a Mapping?)? > - Does the IIS application pool need special configuration? > > I also tried type: "smb", to see how it configures things, but a) it > didn't seem to work (wouldn't get past the port mapping) and most > importantly b) it needs to run as administrator, and I don't want to run > Vagrant as admin. > > In other words, I'm not really interested in getting type: "smb" to work > as a permanent solution, I'm just looking for the right strategy to set it > up manually. > > Thanks, > Jamie > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f1df91cb-473c-467b-8d49-fbcfa72b7af9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
