plug_ribbon alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view plug_ribbon 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 -
react_phoenix
Make rendering React.js components in Phoenix easy -
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. -
sentinel
DEPRECATED - Phoenix Authentication library that wraps Guardian for extra functionality -
phx_component_helpers
Extensible Phoenix liveview components, without boilerplate -
plug_rails_cookie_session_store
Rails compatible Plug session store -
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. -
scrivener_headers
Scrivener pagination with headers and web linking -
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_rest
REST behaviour and Plug router for hypermedia web applications in Elixir -
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
Votex
Implements vote / like / follow functionality for Ecto models in Elixir. Inspired from Acts as Votable gem in Ruby on Rails -
phoenix_html_simplified_helpers
Some helpers for phoenix html( truncate, time_ago_in_words, number_with_delimiter, url_for, current_page? )
Access the most powerful time series database as a service
Do you think we are missing an alternative of plug_ribbon or a related project?
README
plug_ribbon
This Plug module injects a ribbon to your web application in the configured environment.
Used to differentiate between environments.
[](priv/static/screenshot.png)
Motivation
Inspired by rack-dev-mark
Setup
To use plug_ribbon in your projects, edit your mix.exs
file and add plug_ribbon as a dependency:
defp deps do
[
{:plug_ribbon, "~> 0.2.0"}
]
end
Usage
This plug should be one of the last ones in your pipeline.
Add the plug and specify a list of environment atoms that you want the ribbon to be shown.
defmodule MyPhoenixApp.Router do
use MyPhoenixApp.Web, :router
pipeline :browser do
plug :accepts, ["html"]
plug :fetch_session
plug :fetch_flash
plug :protect_from_forgery
plug Plug.Ribbon, [:dev, :staging, :test]
end
pipeline :api do
plug :accepts, ["json"]
end
scope "/", MyPhoenixApp do
pipe_through :browser # Use the default browser stack
get "/", PageController, :index
end
# Other scopes may use custom stacks.
# scope "/api", Observes do
# pipe_through :api
# end
end
After you are done, run mix deps.get
in your shell to fetch the dependencies.
The ribbon will display a label with your current environment in capital letters.
Mix.env |> Atom.to_string |> String.upcase
Testing
$ mix test
License
See the [LICENSE](LICENSE) file for more information.
*Note that all licence references and agreements mentioned in the plug_ribbon README section above
are relevant to that project's source code only.