plug
phoenix_slime
Our great sponsors
| plug | phoenix_slime | |
|---|---|---|
| 6 | 2 | |
| 2,690 | 305 | |
| 0.4% | 0.0% | |
| 0.0 | 0.0 | |
| 4 days ago | 7 months ago | |
| Elixir | Elixir | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
plug
-
Elixir for Cynical Curmudgeons
Yes, it’s a bit of a magic argument, but it’s the only unhygienic variable introduced with a Plug dispatch:
https://github.com/elixir-plug/plug/blob/main/lib/plug/route...
Everything else is explicitly passed, AFAICT.
-
I'm struggling with creating a rest api with Elixir - total noob
Have you read https://github.com/elixir-plug/plug ? Shows you how to do a GET in under 5 mins.
- ElixirのHTTPクライアントでお天気情報を取得したい(2022年)
-
Request Coalescing in Async Rust
Coming from the Ruby ecosystem, a lot of this played out similarly to how the Rack[1] middleware conventions developed in the early Rails v1 and v2 days. Prior to Rack there was a lot of fragmentation in HTTP server libraries, post-Rack everything more or less played nicely as long as libraries implemented Rack interfaces.
I don't write Rust professionally, but it was a bummer seeing that this seems to be a place that was figured out (painfully) in ecosystems used heavily for web development--Javascript and Elixir have their own Rack equivalents[2][3]. I hope that Tower plays a similar role to unify the library ecosystem in Rust.
1. https://github.com/rack/rack
-
Learn how to deploy Elixir apps on Heroku
If you're not familiar with it, feel free to check the inner workings of Plug in their documentation. For now, the code above is fairly self-explanatory I hope. All we need to know is that we're using the Plug.Router capabilities and exposing an endpoint /bpi which we're going to use to retrieve our data and to show it.
phoenix_slime
-
Who wants to fix phoenix_slime with me?
Regarding finding a way to deliniate the HEEx stuff, the issue I linked above (https://github.com/slime-lang/phoenix_slime/issues/92) has a couple of ideas. Should we move the conversation there?
What are some alternatives?
ex_admin - ExAdmin is an auto administration package for Elixir and the Phoenix Framework
phoenix_ecto - Phoenix and Ecto integration with support for concurrent acceptance testing
Raxx - Interface for HTTP webservers, frameworks and clients
phoenix_pubsub_redis - The Redis PubSub adapter for the Phoenix framework
phoenix_live_reload - Provides live-reload functionality for Phoenix
corsica - Elixir library for dealing with CORS requests. 🏖
react_phoenix - Make rendering React.js components in Phoenix easy
filterable - Filtering from incoming params in Elixir/Ecto/Phoenix with easy to use DSL.
phoenix_haml - Phoenix Template Engine for Haml
phoenix_html - Phoenix.HTML functions for working with HTML strings and templates
params - Easy parameters validation/casting with Ecto.Schema, akin to Rails' strong parameters.
phoenix_pubsub_rabbitmq - RabbitMQ adapter for Phoenix's PubSub layer