A declarative and extensible framework for building Elixir applications.
Find a file
2020-08-18 15:46:53 -04:00
.github chore: include #my-elixir-status in tweets 2020-08-17 03:05:31 -04:00
config fix: remove test warning from git_ops 2020-06-01 22:09:26 -04:00
documentation fix: remove bad package reference from the docs 2020-08-15 16:29:56 -04:00
lib fix(extensions): resolve duplicate nested entities 2020-08-18 01:49:35 -04:00
logos chore: add cropped for header 2020-06-03 16:17:15 -04:00
test test(Ash.DataLayer.Ets): add unit tests (#93) 2020-08-18 15:46:53 -04:00
.check.exs feat: extension section module imports, generated .formatter.exs (#71) 2020-06-15 02:40:33 -04:00
.credo.exs test(Ash.DataLayer.Ets): add unit tests (#93) 2020-08-18 15:46:53 -04:00
.formatter.exs feat: add named aggregates 2020-08-08 16:17:52 -04:00
.gitignore fix: stop gitignoring the mnesia data layer 2020-06-30 09:58:04 -04:00
CHANGELOG.md chore: release version v1.8.0 2020-08-18 01:51:07 -04:00
LICENSE WIP 2019-12-04 10:16:34 -05:00
mix.exs chore: release version v1.8.0 2020-08-18 01:51:07 -04:00
mix.lock chore: update to latest git_ops 2020-07-24 17:53:11 -04:00
README.md chore: release version v1.8.0 2020-08-18 01:51:07 -04:00

Logo

Elixir CI License: MIT Coverage Status Hex version badge

ALPHA NOTICE

Ash is in alpha. The package version is 1.0.0+, and most of the time that means stable, but in this case it does not. The 2.0 release will be the stable release.

def deps do
  [
    {:ash, "~> 1.8.0"}
  ]
end

Documentation

All documentation is contained in the generated hex documentation located here. Head there for installation and usage information. What follows is only a brief introduction to Ash.

Introduction

Traditional MVC Frameworks (Rails, Django, .Net, Phoenix, etc) leave it up to the user to build the glue between requests for data (HTTP requests in various forms as well as server-side domain logic) and their respective ORMs. In that space, there is an incredible amount of boilerplate code that must get written from scratch for each application (authentication, authorization, sorting, filtering, sideloading relationships, serialization, etc).

Ash is an opinionated yet configurable framework designed to reduce boilerplate in an Elixir application. Ash does this by providing a layer of abstraction over your system's data layer(s) with Resources. It is designed to be used in conjunction with a phoenix application, or on its own.

To riff on a famous JRR Tolkien quote, a Resourceis "One Interface to rule them all, One Interface to find them" and will become an indispensable place to define contracts for interacting with data throughout your application.

To start using Ash, first declare your Resources using the Ash Resource DSL. You could technically stop there, and just leverage the Ash Elixir API to avoid writing boilerplate. More likely, you would use extensions like Ash.JsonApi or Ash.GraphQL with Phoenix to add external interfaces to those resources without having to write any extra code at all.

Ash is an open-source project and draws inspiration from similar ideas in other frameworks and concepts. The goal of Ash is to lower the barrier to adopting and using Elixir and Phoenix, and in doing so help these amazing communities attract new developers, projects, and companies.

Creating a new release of Ash

  • check out the repository locally
  • run mix git_ops.release (see git_ops documentation for more information)
  • check the changelog/new release number
  • push (with tags) and CI will automatically deploy the hex package