revision_plate_ex alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view revision_plate_ex 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 -
react_phoenix
Make rendering React.js components in Phoenix easy -
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 -
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
recaptcha
A simple reCaptcha 2 library for Elixir applications. -
sentinel
DEPRECATED - Phoenix Authentication library that wraps Guardian for extra functionality -
plug_graphql
Plug (Phoenix) integration for GraphQL Elixir -
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. -
scrivener_headers
Scrivener pagination with headers and web linking -
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 ๐ -
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_statsd
Send connection response time and count to statsd -
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? )
Collect and Analyze Billions of Data Points in Real Time
Do you think we are missing an alternative of revision_plate_ex or a related project?
README
RevisionPlateEx
Plug application and middleware that serves endpoint returns application's REVISION.
See also revision_plate which is implemented with Ruby.
Document is here.
Requirement
Elixir ~> 1.4
Quick use as standalone server
Add revision_plate_ex to your list of dependencies in
mix.exs
:def deps do [{:revision_plate_ex, "~> 0.4.1"}] end
Ensure revision_plate_ex is started before your application:
def application do [applications: [:revision_plate_ex]] end
Create
REVISION
file in root path.Start application
Access to
http://localhost:4000/hello/revision
via browser, then the server return binary written inREVISION
Use with Phoenix
Read document associated with RevisionPlateEx.Hello.revision/1
Configurations
Can use two configurations.
use Mix.Config
config :revision_plate_ex,
http_port: 8000, # Used only standalone mode. Default is `4000`.
file_path: "REVISION" # Used anyone would like to customize path to revision file. Default is "REVISION".
LICENSE
MIT. Read LICENSE file.
*Note that all licence references and agreements mentioned in the revision_plate_ex README section above
are relevant to that project's source code only.