trailing_format_plug
plug
Our great sponsors
- Learn Elixir Learn Elixir in as little as 12 Weeks
- Paraxial.io - Elixir and Phoenix Application Security Platform
- InfluxDB - Access the most powerful time series database as a service
- SonarQube - Static code analysis for 29 languages.
| trailing_format_plug | plug | |
|---|---|---|
| 0 | 4 | |
| 24 | 2,625 | |
| - | 0.6% | |
| 0.0 | 6.7 | |
| over 5 years ago | 7 days ago | |
| Elixir | Elixir | |
| Apache License 2.0 | Apache License 2.0 |
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.
trailing_format_plug
We haven't tracked posts mentioning trailing_format_plug yet.
Tracking mentions began in Dec 2020.
plug
- 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.
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
react_phoenix - Make rendering React.js components in Phoenix easy
corsica - Elixir library for dealing with CORS requests. 🏖
phoenix_slime - Phoenix Template Engine for Slime
phoenix_haml - Phoenix Template Engine for Haml
phoenix_html - Phoenix.HTML functions for working with HTML strings and templates
phoenix_pubsub_rabbitmq - RabbitMQ adapter for Phoenix's PubSub layer
rummage_ecto - Search, Sort and Pagination for ecto queries