on master help sign in
Use lookupEnv instead of getEnvironment to get the value of the PORT environment variable
commit880de5e565b2a3c7c82cb02a0f587474fd8abd7a authorAndrew Martin <andrew.thaddeus@gmail.com> dateThu 28 Mar 2019, 16:28 (8 years ago) parentfce4029
2 files changed+7−2
warp/ChangeLog.md+5 warp/Network/Wai/Handler/Warp/Run.hs+2−2
warp/ChangeLog.md+5
@@ -1,3 +1,8 @@
1+## 3.2.27
2+
3+* Internally, use `lookupEnv` instead of `getEnvironment` to get the
4+ value of the `PORT` environment variable.
5+
16## 3.2.26
27
38* Support network package version 3
warp/Network/Wai/Handler/Warp/Run.hs+2−2
@@ -23,7 +23,7 @@ import Network.Socket (Socket, close, accept, withSocketsDo, SockAddr(SockAddrIn
2323import qualified Network.Socket.ByteString as Sock
2424import Network.Wai
2525import Network.Wai.Internal (ResponseReceived (ResponseReceived))
26−import System.Environment (getEnvironment)
26+import System.Environment (lookupEnv)
2727import System.Timeout (timeout)
2828
2929import Network.Wai.Handler.Warp.Buffer
@@ -80,7 +80,7 @@ run p = runSettings defaultSettings { settingsPort = p }
8080-- Since 3.0.9
8181runEnv :: Port -> Application -> IO ()
8282runEnv p app = do
83− mp <- lookup "PORT" <$> getEnvironment
83+ mp <- lookupEnv "PORT"
8484
8585 maybe (run p app) runReadPort mp
8686