SAFE Template using Elmish.Bridge & LiteDB.FSharp

This is a fork of SAFE-template-extended, replacing Fable.Remoting with Elmish.Bridge. This gives an Elmish architecture to the client-server communication, and brings with it a websocket layer instead of the HTTP used by Remoting.

Again, this was a learning exercise for me.

I deployed this to Azure, but it seems that Azure isn't happy about websockets. That would have been cool for people to see, since you will now see other people's edits appear in real-time (not ideal for a todo app!). You can download and build the repo yourself easily enough. Open up two browsers to localhost:8080 and watch the edits mirror to the other browser.

To build and run:

git clone https://github.com/davedawkins/SAFE-template-Bridge-LiteDB
cd SAFE-template-Bridge-LiteDB
dotnet tools restore
dotnet fake build --target run

Open a browser at localhost:8080. Open another one to see the broadcasting in effect.

I learned the basics of Elmish.Bridge from Zaid-Ajaj/tabula-rasa.

Here's the original README for SAFE-template-extended:

This template was created with dotnet new safe from SAFE Stack. I've then added the following features to approach something closer to the standard TodoMVC example.

Server:

replaced the in-memory storage with LiteDB using LiteDB.FSharp.
replace Fable.Remoting with Elmish.Bridge (new)

Client:

option to use in-memory storage so that I can run a live demo (see below) on github.io
added view filters
return key will add new todo
double-click to edit existing do
checkbox to toggle todo complete
(x) button to delete todo
(clear completed) button to delete all completed todos
style.css

Build:

publish.js, PublishApp target in build.fsx to support publish to gh-pages