Paul Schoenfelder

@nerdyworm I made some further changes today, can you try again? I'm able to run the foreground and console commands in an administrative console with a release built with `include_erts:...

@OvermindDL1 Yeah I mean, that's kinda my question. Or perhaps multiple questions: 1.) Are the bulk of Windows users looking to deploy Elixir in a situation where they can run...

Thanks for the feedback @OvermindDL1! I will explore the PS route a bit. Since we already have a shim script to exec the "real" boot script, it can be modified...

@vans163 @nerdyworm Thanks for chiming in! It sounds like WSL is still not a practical requirement for production apps, which is a shame given how long it's been around now,...

@OvermindDL1 Yeah some parts will for sure be testable on Linux, which is huge, one of the most complicated parts is the installation and management of the Windows service though...

Well ultimately that's what [erlsrv](http://erlang.org/doc/man/erlsrv.html) is for, so it takes care of most of that - maybe complexity wasn't the right word, more that it is prone to issues if...

I've rewritten all of the Windows scripts in Powershell. It's better if you can run Powershell Core/6+, since I can easily test many things on my macbook with Powershell Core,...

@jfrolich Thanks for the feedback! It supports Distributed Erlang, as the hosts for the application run in the same subnet, so traffic between those hosts is unrestricted. That said, the...

> Most of this is a generic AWS deployment strategy. Which is actually really helpful, but I guess a lot of people are coming to deploy Elixir. So it might...

I think code like that is quite error prone unfortunately, for example, status 206 means it's only partial content, and not all 200 status codes return a response body (e.g....