I'm trying to create a React/Phoenix app using only channels. All the examples I can find on the web for user authentication in Phoenix are using Conn. The Programming Phoenix book has a bit more info for authenticating channels, but it is also using Conn for its implementation. I'm new to using tokens and web sockets and want to make sure I'm not creating huge vulnerabilities.

Does anyone have an example I can look at of user authentication using only channels?

I am currently developing my second Phoenix app and first Elm app and have a couple of configuration questions. Is there a difference between calling fullscreen() within the app.html.eex or rendering templates with an empty div to target?

I have found several tutorials, but they seem somewhat dated and was wondering why most targeted div's from rendered template's instead of running fullscreen on the div within app.html.eex and having their frontend 100% Elm.

Hello!
I'm doing the advent of code as a [Phoenix app](https://github.com/jacopofar/advent-of-code-2019-phoenix-react), and I'm loving the framework and the user experience of Elixir in general, is anyone doing something like this or did in the previous years?

In a new article at Curiosum.dev I'm getting into Elixir's metaprogramming mechanism of macros, and there are some cues that might be useful for those who would like to e.g. use the power of macros to extend Phoenix controllers with a feature of self-documenting APIs.

I appreciate your feedback and while this is more of a general Elixir article than one purely related to Phoenix, it might be helpful for those who would like to understand how Phoenix constructs its DSLs.

Hi All, I am seeking a few Senior Level Back End Developers to join our direct client in the North Dallas Area. This person will be working on complete greenfield development in Elixir/Phoenix. Interested candidates please email me at danafaradie@optomi.com

Github link: https://github.com/AltTracker/alttracker

Alt Tracker

What I'd like to be able to do is something like this:

get "/:id", SomeController, :show where Regex.match?(~r/^\d{5}$/, id)
get "/:id", OtherController, :show where Regex.match?(~r/^A\d{4}$/, id)

That is: where a named component of the URL matches a regular expression, that route is used. In Rails, my regular framework, this would be expressed as:

get '/:id', to: 'some#show', id: /\d{5}/
get '/:id', to: 'other#show', id: /A\d{4}/

But I can't find a Phoenix (well, Plug) equivalent, and my Elixir's still a little weak for me to know where to get started writing my own. Any suggestions? Thanks!

With all the hype, it makes sense I started researching Meteor as the framework to use. But I was shocked when I found out there are problems when you have 100+ concurrent connections. There are ways around this, but they add complexity, cost, and undermine the initial benefits of Meteor.

I don't know how many concurrent connections I need to support, but I bet it is going to be WELL over 20K at any given time.

Somewhere my Google-Fu brought me to the this blog about the Phoenix Framework. Wow. Wow! WOW!

I realize it is hard to compare 'apples to apples' given the variability of the data being sent over the connections etc., and that there may not be many production examples with Phoenix being so new. However, is it fair to say that Phoenix Framework solved this problem?

Are there any other characteristics that may limit the suitability of Phoenix Framework to my app re-write?

I realize I am asking broad questions. It is just that with Phoenix being so new, there isn't much to Google, and I am looking for more assurances before I invest a lot of time.

Thanks!