<FromGitter>
<anamba> trying to use the new Passenger 6 with amber, not having much luck so far. both the amber process and the PassengerAgent process max out the cpu. but while that's happening, i can curl the amber process directly and it responds as expected. hmm...
<FromGitter>
<elorest> Not sure why you would use passenger with amber/crystal. Nginx makes sense. I have a server which I run multiple crystal and rails apps on. I use passenger for rails and straight nginx to proxy amber.
<FromGitter>
<Blacksmoke16> nginx 👌
snsei has quit [Ping timeout: 252 seconds]
<FromGitter>
<anamba> most people probably wouldn't want to add an extra layer like passenger. my job is part hosting and part dev (you could call it devops i suppose, but i'm not a huge fan of that term, plus i don't usually do both jobs for each project). i have a puppet-powered hosting system that lets me throw a bunch of sites on a server without really caring what language/platform they use (i don't think i worded that right, but
<FromGitter>
... hopefully you get the idea). i'm hoping passenger 6 will help me simplify that setup a lot, so that as the hosting director i only have to deal with passenger, and the app developers can specify a passenger config that makes their app run well.
<FromGitter>
<anamba> the other minor detail is that when hosting a lot of sites, i greatly prefer using unix sockets vs trying to find a port that's not in use. amber doesn't support that mode of operation (i'm guessing websockets is the reason), but if i run it through passenger then passenger handles figuring out which port to use, and exposes a socket that i can proxy to.
snsei has joined #amber
<FromGitter>
<anamba> in any case, this issue with passenger is clearly not an amber-specific issue, it does the same thing with the hello world example in the API docs for HTTP::Server
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
<FromGitter>
<anamba> the plot thickens... passenger 6 + amber works great (really great!) on xenial (the server with the issue was upgraded to bionic)
snsei has quit [Ping timeout: 252 seconds]
snsei has joined #amber
snsei has quit [Ping timeout: 268 seconds]
snsei has joined #amber
snsei has quit [Ping timeout: 268 seconds]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
snsei has quit [Remote host closed the connection]
snsei has joined #amber
<FromGitter>
<elorest> Interesting. If you could write up a blog post on that after you figure that out I'm sure that would be useful. I've never thought of using passenger for something like this.
snsei has quit [Remote host closed the connection]
<FromGitter>
<naiyt> Has anybody here had a problem on macOS with getting the `Do you want the application "<app name>" to accept incoming network connections?' message every time `amber watch` recompiles?
snsei has joined #amber
snsei has quit [Remote host closed the connection]