Comments (5)
Thanks! Hadn't crossed the bridge of working with Elixir releases yet, so I'll take your word on this & push out the fix. :)
from remote_ip.
By the way, do you know of an easy way to tell what will or won't break a release? There are two other declared deps that don't have corresponding applications:combine
and plug
.
I suppose plug
will probably be included as an application in whatever project you're using remote_ip
with already. Do you know if combine
will similarly break releases?
from remote_ip.
Oh I completely forgot to answer... Actually you have to add every dependency you are using in production. Elixir 1.4 will automate this and you don't have to define them anymore.
In applications
you add all dependencies that are running as application, and in included_application
you add libraries.
Plug is already included in phoenix. Actually you probably also have to add combine
in included_applications
.
You can read about it here http://blog.plataformatec.com.br/2016/07/understanding-deps-and-applications-in-your-mixfile/
from remote_ip.
@philipgiuliani Thanks for the follow-up! I've only now just gotten around to addressing this, myself. :)
Application inference sounds super useful. I see Elixir 1.4 was just released recently, I'll definitely have to play around with it.
In the meantime, I verified that (indeed) the lack of :combine
breaks when trying to use RemoteIp.Headers.Forwarded
from a Distillery release. (First time using Distillery, actually, so it's a learning process for me.) I'll add :combine
to the :included_applications
- and what the heck, even add :plug
to the :applications
, just to cover all the bases.
from remote_ip.
Yes perfect, so you can also use it without using Phoenix. Great job! With Elixir 1.4 you can just remove all of this :)
from remote_ip.
Related Issues (16)
- @reserved is incorrect HOT 1
- problem with rewritten IP HOT 2
- :combine should not be in :included_applications
- Dialyzer warning HOT 5
- Question about mapped-ipv4 ipv6 format HOT 3
- Export `RemoteIp.Block` as its own package? HOT 8
- X-Forwarded-For is parsed incorrectly! HOT 3
- Good article on `x-forwarded-for` parsing HOT 10
- Unsure of Implementation HOT 5
- Support for `Fly-Client-IP`? HOT 7
- Plug.Conn also has get_peer_data, which returns the original ip HOT 3
- Parse X-Forwarded-Port and X-Forwarded-Proto HOT 3
- Doesn't Work Running Server in Docker Container HOT 5
- Any way to pass runtime information to `init` HOT 1
- RFC1918 IPs shouldn't be discarded by default HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from remote_ip.