ashes alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view ashes alternatives based on common mentions on social networks and blogs.
-
ex_admin
ExAdmin is an auto administration package for Elixir and the Phoenix Framework -
phoenix_html
Phoenix.HTML functions for working with HTML strings and templates -
phoenix_ecto
Phoenix and Ecto integration with support for concurrent acceptance testing -
absinthe_plug
Plug support for Absinthe, the GraphQL toolkit for Elixir -
phoenix_live_reload
Provides live-reload functionality for Phoenix -
params
Easy parameters validation/casting with Ecto.Schema, akin to Rails' strong parameters. -
phoenix_pubsub_redis
The Redis PubSub adapter for the Phoenix framework -
dayron
A repository `similar` to Ecto.Repo that maps to an underlying http client, sending requests to an external rest api instead of a database -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
sentinel
DEPRECATED - Phoenix Authentication library that wraps Guardian for extra functionality -
plug_rails_cookie_session_store
Rails compatible Plug session store -
phx_component_helpers
Extensible Phoenix liveview components, without boilerplate -
filterable
Filtering from incoming params in Elixir/Ecto/Phoenix with easy to use DSL. -
multiverse
Elixir package that allows to add compatibility layers via API gateways. -
access pass
provides a full user authentication experience for an API. Includes login,logout,register,forgot password, forgot username, confirmation email and all that other good stuff. Includes plug for checking for authenticated users and macro for generating the required routes. -
better_params
Cleaner request parameters in Elixir web applications ๐ -
scrivener_headers
Scrivener pagination with headers and web linking -
phoenix_pubsub_rabbitmq
RabbitMQ adapter for Phoenix's PubSub layer -
plug_checkup
PlugCheckup provides a Plug for adding simple health checks to your app -
plug_rest
REST behaviour and Plug router for hypermedia web applications in Elixir -
Votex
Implements vote / like / follow functionality for Ecto models in Elixir. Inspired from Acts as Votable gem in Ruby on Rails -
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
phoenix_html_simplified_helpers
Some helpers for phoenix html( truncate, time_ago_in_words, number_with_delimiter, url_for, current_page? ) -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host.
Elixir and Phoenix Application Security Platform
Do you think we are missing an alternative of ashes or a related project?
Popular Comparisons
README
Ashes
A code generation tool for the Phoenix web framework.
defp deps do
[{:ashes, ">= 0.0.3"}]
end
Controllers
Generates a controller with a given name, will also generate a view and create a folder
for you to put related .eex templates in. Don't forget to add the controller in routes.ex
$ mix ashes.generate controller <controllername>
# web/router.ex
defmodule MyApp.Router do
...
scope "/", MyApp do
resources "/my", MyController
end
end
Will give you the following functions by default:
- index
- edit
- new
- show
- create
- update
- delete
Options
--skip-form
- removes theedit
andnew
functions from the controller (likely used for APIs)--skip-view
- doesn't create a view module--skip-template
- doesn't create a folder for templates
Channels
Generates a channel with the given name. Don't forget to add the channel to your router
$ mix ashes.generate channel <channelname> [events]
# routes.ex
defmodule MyApp.Router do
...
socket "/ws", MyApp do
channel "my:*", MyChannel
end
end
Will give you the following functions by default:
join(_topic, message, socket)
leave(_reason, socket)
If you provide events in the generate command, they will be added to the channel as
def handle_in("eventname", message, socket) do
{:ok, socket}
end
Models
Generates an Ecto model with the given name and schema. Requires ecto!
$ mix ashes.generate model <modelname> [schema entries]
Schema entries should be of the form name:type
with types being defined by ecto.
Options
--timestamps
- adds ecto timestamps to your schema.
Migrations
Assumes a valid repo module name of MyApp.Repo
Generates an Ecto migration with the given name. Requires ecto
$ mix ashes.generate migration <migrationname>