Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
I ended up just making my own UserSession class and storing session data in a dictionary
How do we get the logs out of Suave now?. It seems like all the docs point to using logary adapters (or to projects that have had logary ripped out), and either way of initializing the facade (via the adapters initialize or via createGeneric and parsing it in) seem to be exquivalent to piping to /dev/null
@btrepp I'm using Log4net in the C#-ish way. So each modules declares log = log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType) on top, then and I can use log.Debug() or something similar where I need, and it does work fine. There is the need to configure it by adding a proper log4net.config file, and a line like [<assembly: log4net.Config.XmlConfigurator(ConfigFile = "log4net.config")>] in AssemblyInfo.fs. I don't remember exactly where I found such info. I just know it works anyway.
@haf I wanted a single thing I could use for either pathScan or sprintf
I'm a suave and f# beginner having a question: Why do you want to run a Suave as a .fsx script and why not as a .fs?
I've gone down the .fs road but I got stuck trying to get Suave to work in my app together with docker... "Console.ReadKey true |> ignore" doesn't seem to work in a Docker environment for some reason and without it my Suave app just exits immediately. Any tips?
@ademar Thanks for the tip. I've basically only copied the code on the suave introduction page: https://suave.io/index.html
open System
open System.Threading
open Suave
[<EntryPoint>]
let main argv =
let cts = new CancellationTokenSource()
let conf = { defaultConfig with cancellationToken = cts.Token }
let listening, server = startWebServerAsync conf (Successful.OK "Hello World")
Async.Start(server, cts.Token)
printfn "Make requests now"
Console.ReadKey true |> ignore
cts.Cancel()
0 // return an integer exit codebut if I remove Console.ReadKey it becomes nonblocking.
Is the key not to use startWebServerAsync and rather use startWebServer as u mentioned?
- trying it out now *
Further to question from @farzadfusion, there is an example of a service file in a response to Issue #218. Unfortunately, that example hasn't worked for our deployment of a Suave server on Digital Ocean. SuaveIO/suave#218
@farzadfusion check out this thread https://www.reddit.com/r/fsharp/comments/7ydhct/how_to_auto_start_suave_app/
<input type="hidden" id="custId" name="custId" value="3487">
hi. i'm trying to revive suave proxy functionality as existing here: https://searchcode.com/codesearch/view/109236858/
unfortunately without success yet. there is too much api changes and without insights into internals. this is my current state: https://gist.github.com/haraldsteinlechner/0b3eb4eea492162d223c6f3d5516f744
what happened to socketpart?
yeah we dropped SocketPart and proxy at some point .. still i think it should be possible to shape the function proxy into a webpart .. just change it a bit till you get the correct signature .. I'll look into it later today if you don't beat to me to it .. i will very much would like to have proxy back in
what was the idea of heaving to different delayed httpcontexts here in the first place?
btw this is my last state: https://gist.github.com/haraldsteinlechner/2cd9eeafb444092b035ed83904a13ede
ok this is my progress. currently i'm struggling to support websockets... haraldsteinlechner/suave2@939d52e
also, i'm not sure, i think my current implementation is superslow, since all is on a per-request level? for websockets we could initiate handshake at some point, if we are sure it is on per-connection level. iwould be great if you can think this stuff through.
this is where it gets complicated .. for proxying it would be optimal if suave didn't waste time parsing POST payloads or websockets segments and it just copied the bytes over. this is not possible to express in the webpart paradigm .. it would need to be built out of more fundamental constructs.
Hi, I ported a small Suave program from mono to .net core. Basically now I can run "dotnet run" and it works. But the webserver seems unable to retrieve files like .css and images. The webpart contains an entry like pathRegex "(.*).(css|gif|js|png|jpeg|jpg|)" >=> Files.browseHome, and I tried making the jpeg files and the css available under the current dir , and also the dir where the assembly is deployed (i.e. bin/Debug/netcoreapp2.1), but seems impossible to see those files. Help is appreciated. Thanks. Ciao.
By default suave application on my Mac doesn't serve to the outside world. Only accepts connections from localhost.
There's probably a setting somewhere that enables connections to the outside world