Does anyone have any favorite open-source Phoenix codebases?
hexpm the package manager website is open source:
https://github.com/hexpm/hexpm
Firestorm is another:
Phoenix 1.3.0 Released
91–100 of 143 posts
Re: Phoenix 1.3.0 Released
#92Does Phoenix 1.3.0 fully support Elixir 1.5? I keep getting warnings when compiling since I upgraded to Elixir 1.5.
It does. You may also need to upgrade your mix dependencies, I'm sure many of their authors are busy fixing the deprecation warnings as I type
Re: Phoenix 1.3.0 Released
#93Would you suggest to choose Elixir / Phoenix for an api for a startup? Is it too risky now, or good enough + very attractive?
Jump in, the more the merrier!
Re: Phoenix 1.3.0 Released
#94How is it better than F# and Akka.NET?
Re: Phoenix 1.3.0 Released
#95Earlier quoted context omitted.
Elixir in Action is a bit outdated, no?
I read it a while ago, but I remember it being pretty useful. Some of the elixir bits are now out of date. (eg. it still has a section on Records) But it touched on a lot of OTP topics that were missing from other places. (this was before Benjamin Tan's book was finished) At the time I remember Elixir in Action really made me finally understand the OTP concepts.
Just want to point out that Records are still part of the standard library, and can be important for integrating with Erlang code using records which you need to work with. Even though they are avoided in Elixir, because structs are better in every way, they are still alive and well in Erlang.
Re: Phoenix 1.3.0 Released
#96How are people hosting their Phoenix projects? I'm used to Heroku or Laravel Forge. I don't really want to mess too much with servers.
In a datacenter on bare metal :-)
I also work on a number of side projects with coworkers and we host those in Heroku. Can't really speak to how well that'd work if they were more than just side projects, but it works for us.
Re: Phoenix 1.3.0 Released
#97Quote interesting release, many useful features. `action_fallback` looks really nice. Contexts ... not so much imo
Contexts are just the default now. Nothing is preventing you from doing things the old way, or from using them in 1.2 without upgrading. If you can think of a better architecture that doesn't involve contexts, then that should absolutely be what you're doing.
Re: Phoenix 1.3.0 Released
#98Earlier quoted context omitted.
Even rails doesn't ship with an auth module though. Lots of people use Devise and there is an equivalent for Elixir (Coherence)...but shipping with auth built in is an exploit waiting to happen IMO.
Rails ships with an auth module: http://api.rubyonrails.org/classes/ActiveModel/SecurePasswor...
has_secure_password is not an "auth module". That's simply a handy function to handle a password attribute... which an actual auth module can make use of if it desired.
Re: Phoenix 1.3.0 Released
#99For anyone curious about Phoenix and Elixir, I can sincerely recommend the following resources to get you started: - Programming Phoenix by Chris McCord, Bruce Tate, and José Valim [1] - The Little Elixir & OTP Guidebook by Benjamin Tan Wei Hao [2] - Elixir in Action by Saša Jurić [3] Phoenix initially attracted me to Elixir, I've stuck around for that and the OTP platform: pattern matching, process based concurrency…
Another great resource that was recently released is the Phoenix Inside Out series by Shankar: https://shankardevy.com/phoenix-book/ I just got it a few days ago and I'm about 30% into the first book. What I can say so far is that the author's approach resonates really well with me. Going through the book feels like sitting next to a colleague, who is introducing you to Phoenix and is really knowledgeable in the topi…
> If you have previous experience in another MVC framework and are interested in Phoenix I highly recommend this series (at least based on what I've read so far).
Do you need Elixir experiences too?
I've done MVC and have some functional experiences.
I've seen this book but wasn't sure if it was for me and decided to do exercism's elixir exercises before buying this book.
thanks
Re: Phoenix 1.3.0 Released
#100Earlier quoted context omitted.
For me the sweet spot is somewhere in between. If it just shipped with a decent auth module that would work for 90% of people, but that could also be easily replaced or extended if needed, that would be the best of both worlds.
Even rails doesn't ship with an auth module though. Lots of people use Devise and there is an equivalent for Elixir (Coherence)...but shipping with auth built in is an exploit waiting to happen IMO.
Laravel does, and their more batteries included approach is nice in my opinion