Phoenix GraphQL Tutorial with Absinthe: Authentication with Guardian - Ryan Swapp
This is the third post in a series on using Phoenix and GraphQL to create clean and powerful API’s. In this post I will cover adding authentication to our API with Guardian. For those who are just joining us, I recommend starting with the first post before starting this one. However, you can start where we left off last time by cloning the repo and checking out the checkpoint-2 branch. If you go t
Comparing Rails and Phoenix: Part I
As I was thinking about this article a few weeks ago, I was excited when I saw that Chris McCord, creator of the Phoenix Framework in Elixir, was on the Elixir Fountain podcast. One of the things they mentioned on the show was that they were tired of the comparison being made between Rails and Phoenix. The bias of coming from a Rails background may cloud your view of the framework and cause you to
Mocks and explicit contracts « Plataformatec Blog
UPDATE: Almost 2 years later we have released a tiny library called Mox for Elixir that follows the guidelines written in this article. A couple days ago I expressed my thoughts regarding mocks on Twitter: Mocks/stubs do not remove the need to define an explicit interface between your components (modules, classes, whatever). [1/4] — José Valim (@josevalim) September 9, 2015 The blame is not on moc
Beyond 10,000 Lines: Lessons Learned from a Large Phoenix Project
We recently finished up a large Phoenix project at Infinite Red, and we learned some tips and tricks along the way that I want to share. Overall, we’ve been impressed at how well organized and maintainable a Phoenix project can be beyond 10,000 lines of code. Some of the tips in this post are specific to Phoenix, others could be equally applied to Rails or other web frameworks. None of them are me
まだRailsで消耗してるの？
https://cw-meetup.doorkeeper.jp/events/52879 での発表資料
ElixirとPhoenixでWebSocketを使ったChatアプリケーションを作る | DevelopersIO
昨今のWebアプリケーションでは、クライアント、サーバが常時接続してメッセージ通信をすることが求められてきています (リアルタイムWebアプリケーションと呼ばれたりします)。 このアプリケーションには以下の特徴があります クライアント、サーバが常時接続 クライアントからではなく、サーバから接続しているクライアントへ情報をプッシュする 通信の頻度が多い 今回はこのような常時接続型のアプリケーションを実現するために作られたWebSocketの説明と、PhoenixでWebSocketをどのように使って常時接続のアプリケーションを作るか説明します。 WebSoketが必要とされてきた背景 今までのWebアプリケーションのリクエスト/レスポンス処理は以下のようなアーキテクチャでした。 全てのリクエストは状態を持たない サーバはリクエストを毎回新しいものとして扱う(HTTPはもともとステートレスなプ
Elm and Phoenix/Elixir in production for France TV
Are Elm and Phoenix/Elixir ready for prime time? I’ll let you decide: they were both used in live during the main French political show called “L’émission Politique” to help generate a word cloud based on the guest speech. To the date of this writing, the guests were Nicolas Sarkozy (12 millions viewers), Arnaud Montebourg (9 millions) and lately Alain Juppé (13 millions). tl;dr: Elm allowed me to
Rails使いがElixirのEctoを勉強した時のまとめ - Qiita
Rubyに影響を受けた(というより弟分)言語であるElixirが熱いです。 RailsインスパイアのElixirのWAFであるPhoenixはrailsの10倍早いらしいです。 何かと話題の関数型言語elixir + phoenixを勉強中にデータベースラッパー&クエリジェネレータであるEctoの使い方がrailsのActiveRecordとは違う雰囲気で色々と悩んだのでメモ。Ecto単体で使った場合なのでphoenixと一緒に使った場合は違う部分があるかもしれません。 全体的にパイプライン演算子(|>)を存分に使ったコードで楽しいです。キーワードクエリはSQLっぽくてどうにも好きになれないので基本的にパイプラインクエリを使っています。 「こっちの方が適切」「もっとイケてる書き方がある」「phoenixではこう書ける」「phoenixでは使えない」等ありましたらコメントお願いします。 準備
Internationalization using Gettext in the Phoenix framework
Written using Phoenix 1.1 Internationalization - what is it? Internationalization (henceforth called i18n, because programmers are lazy and hate typing long words) is the process of adapting a web application for use in different languages or cultures. Any application that allows you to change your language has implemented i18n. It's a close sibling of localization (L10n) - the process of actually
Implementing Video Chat in a Phoenix Application with WebRTC
by Chad Brading on September 16, 2015 In this blog post we’re going to cover how to implement video chat in a Phoenix application with WebRTC. By the end of this post we will have enabled two remote clients to connect with each other and engage in a video conversation. We will use Phoenix channels to communicate messages between our two clients so they can establish a remote peer connection. WebRT
Excellent Talks from Elixir & Phoenix Conf 2016 | Grok Interactive
In addition to the delicious lunches and snacks, beautiful location, friendly people and excitement in the air, Elixir and Phoenix Conf 2016 delivered some awesome talks. Here are our favorites: Opening Keynote by Chris McCordPhoenix – Getting realtime with channels. Keynote by José ValimGenStage and Flow. Closing Keynote by Boyd MultererElixir for the next 10 years. Abstractions: A Tale of Keys a
Writing A Full Site in Phoenix and Elm
Last UpdatedJune 29th, 2016 Current VersionsElixir: v1.2.6, Phoenix: v1.1.6, Elm: v0.17 IntroductionElixir is a very nice functional language, and with Phoenix, we can use it to build very nice backends to our web applications. The trouble is, however, that as more and more sites become JavaScript-heavy, we lose our nice functional language to go work in those other languages. What are our options
Setting up Elm with Phoenix
Updated: 05/18/2016 Current VersionsElixir: v1.2.5 Phoenix: v1.1.4 Elm: v0.17.0 Elm-Brunch: v0.4.4 NPM: >3.x Node: >5.x Brunch: >2.1.x Step 1: Creating our applicationWe’ll start by creating our Phoenix and Elm application the same as we’d create any other Phoenix application. If you need instructions on how to install Phoenix, you can consult the Phoenix Framework site at http://www.phoenixframew
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Why is Elixir/Phoenix gaining so much adoption in the software development industry?
jeremybellows.com
How Stateful Web Applications work - Thoughts & Bots
GitHub - smpallen99/webrtc_example: Example webrtc peer to peer with server using Phoenix Channels
GitHub - bharani91/ex-shop: Digital goods shop & blog created using Elixir (Phoenix framework)
GitHub - knewter/time-tracker: An example Single Page Application in Elm, using elm-mdl for the UI, with a Phoenix backend.
Phoenix Channels vs Rails Action Cable - DockYard
