kolektiv.github.io
LambdaConf 2015
https://kolektiv.github.io/conferences/2015/05/27/lambdaconf
Last week I was lucky enough to be at LambdaConf 2015 in Boulder, CO. While there I gave a workshop on Freya. Which was fun (for me at least, hopefully for the attendees). I’ve got a few blog posts percolating from my experiences (mainly about how LambdaConf made me feel about the good and the bad of the current F# world), but to start the mental process actually running:. First of all, if you can get to LambdaConf 2016 -. For more stuff from me, take a look here.
docs.freya.io
Core — Documentation — Freya
https://docs.freya.io/en/latest/reference/core/index.html
Provides the basic abstractions on which the Freya stack is built. Most of the types and basic functionality used by the higher level parts of Freya depend on the basics defined in Freya.Core. These essential elements of Freya are defined in the following sections:. Content 2013-2016 Andrew Cherry. Documentation kindly powered by ReadTheDocs. Offer Freya and F# consultancy for your projects.
xyncro.tech
Xyncro Tech / Freya / Freya
https://xyncro.tech/freya
Freya is a functional web programming stack designed to emphasise functional programming principles, compositionality and high levels of safety and abstraction. It supports multiple web servers and is portable across all servers/environments with OWIN support. It is significant enough in scope to have it’s own site and documentation please see freya.io.
docs.freya.io
Polyfills — Documentation — Freya
https://docs.freya.io/en/latest/reference/polyfills/index.html
Polyfills provide functionality which is not (and may never be) part of an open standard. Existing polyfills add existing data to the OWIN standard, enabling such things as more accurate routing. Polyfills are available for the following servers:. 8211; polyfills for Katana-based implementations, including self-hosted and IIS hosted approaches. 8211; polyfills for Kestrel-based servers. Content 2013-2016 Andrew Cherry. Documentation kindly powered by ReadTheDocs.
docs.freya.io
Types — Documentation — Freya
https://docs.freya.io/en/latest/reference/types/index.html
Freya is driven by a strongly-typed approach to working with the web, and so includes a set of libraries ( Freya.Types.*. Which model many of the constructs found in web specifications, particularly those dealing with HTTP, URIs, etc. These libraries were previously known as the Arachne project, but were brought under the Freya umbrella in the 3.0 release. Content 2013-2016 Andrew Cherry. Documentation kindly powered by ReadTheDocs. Offer Freya and F# consultancy for your projects.
docs.freya.io
Reference — Documentation — Freya
https://docs.freya.io/en/latest/reference/index.html
Reference documentation for Freya contains guides to specific libraries along with guides for using Freya as part of a larger system. These are technical guides and give an overview of general use, rather than a recipe-like approach. The reference documentation is designed to be referred to when you’re using Freya. 8211; for focused guides to areas of development with Freya. 8211; for Freya-based solutions to common problems. Content 2013-2016 Andrew Cherry. Documentation kindly powered by ReadTheDocs.
docs.freya.io
Policies — Documentation — Freya
https://docs.freya.io/en/latest/meta/policies.html
Freya does not have a large set of policies, but some aspects of the project do require explicit affirmation of expectations. Please read the following on conduct! Were Freya to adopt a formal code of conduct, it would probably look rather like the Rust Code of Conduct. 8211; please refer to that document for the kinds of behaviour expected of people taking part in the Freya community. Open source software matters, but it matters less than people. Content 2013-2016 Andrew Cherry.
docs.freya.io
Integration — Documentation — Freya
https://docs.freya.io/en/latest/recipes/integration.html
Integrating Freya with other systems (whether servers to host Freya applications, or other software frameworks) is essential. Freya should integrate widely through the use of the OWIN open standard, but it is not always obvious how it should work in practice. Examples and information for integration are given in the following two recipe sections:. 8211; integrating Freya with servers for hosting. While OWIN is an open standard, the approaches to integrating OWIN vary between server implementations.
docs.freya.io
Community — Documentation — Freya
https://docs.freya.io/en/latest/meta/community.html
The F# community is a friendly place and we hope for the same for Freya. We encourage everyone to come and talk in our Gitter channel. Where all are welcome. It’s a great place to ask questions! For keeping up to date with news on Freya and the ecosystem around it, follow Freya on Twitter. 8211; any news, changes, announcements, releases, etc. will be posted there, along with new blog posts, etc. Most of all, we encourage you all to get involved, try Freya out, and tell us what you think!
SOCIAL ENGAGEMENT