Skip to content
A simple example of setting up websockets using SAFE
F# JavaScript Dockerfile CSS HTML
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.devcontainer Initial commit Mar 6, 2020
.paket Initial commit Mar 6, 2020
.vscode Initial commit Mar 6, 2020
src Work on web sockets Mar 7, 2020
.editorconfig Initial commit Mar 6, 2020
.gitignore Initial commit Mar 6, 2020
README.md Initial commit Mar 6, 2020
RELEASE_NOTES.md
build.fsx Initial commit Mar 6, 2020
package.json Initial commit Mar 6, 2020
paket.dependencies
paket.lock Initial commit Mar 6, 2020
safechannels.sln Initial commit Mar 6, 2020
webpack.config.js Initial commit Mar 6, 2020
yarn.lock Initial commit Mar 6, 2020

README.md

SAFE Template

This template can be used to generate a full-stack web application using the SAFE Stack. It was created using the dotnet SAFE Template. If you want to learn more about the template why not start with the quick start guide?

Install pre-requisites

You'll need to install the following pre-requisites in order to build SAFE applications

  • The .NET Core SDK
  • FAKE 5 installed as a global tool
  • The Yarn package manager (you an also use npm but the usage of yarn is encouraged).
  • Node LTS installed for the front end components.
  • If you're running on OSX or Linux, you'll also need to install Mono.

Work with the application

To concurrently run the server and the client components in watch mode use the following command:

fake build -t Run

SAFE Stack Documentation

You will find more documentation about the used F# components at the following places:

If you want to know more about the full Azure Stack and all of it's components (including Azure) visit the official SAFE documentation.

Troubleshooting

  • fake not found - If you fail to execute fake from command line after installing it as a global tool, you might need to add it to your PATH manually: (e.g. export PATH="$HOME/.dotnet/tools:$PATH" on unix) - related GitHub issue
You can’t perform that action at this time.