4 ms·
What’s the alternative? I was deploying from a Mac, so connecting to a Unix box is exactly what I was doing.
by simulate-me 5y ago
What’s the alternative? I was deploying from a Mac, so connecting to a Unix box is exactly what I was doing.
- pjmlp 5y agoA possible alternative. https://support.apple.com/guide/mac-help/share-mac-files-with-windows-users-mchlp1657/mac https://support.apple.com/guide/mac-help/share-mac-files-wit... https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-mac https://docs.microsoft.com/en-us/windows-server/remote/remot... Another alternative, https://docs.microsoft.com/en-us/powershell/scripting/learn/remoting/running-remote-commands https://docs.microsoft.com/en-us/powershell/scripting/learn/...
- simulate-me 5y agoI was deploying to a fleet of servers. Having every engineer add every server via the macOS sharing UI or using RDP to manually connect to each host doesn’t seem scalable. Maybe remote power shell sessions would work, but I’m not even sure if there is a power shell client for Mac, and it’s also not clear if remote power shell sessions would fix the open file handle issue. Experienced Windows devs I talked to said they used Packer from Hashicorp to entirely recreate their server image whenever they wanted to deploy. This process takes hours, but that was the best I found.