GitHub - gaynetdinov/ex_marshal: Ruby Marshal format implemented in ElixirYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
The Pragmatic Studio
“If you are looking for deeply technical and immersive video training, @pragmaticstudio is a steal. The pacing and content is second to none in my experience!” As software makers, being able to learn new things quickly and well is a superpower. That's why we create clear and concise video courses for busy developers. Courses that are up-to-date, to the point, and quickly move you from confusion to
Phoenix vs Rails: Views and helpers - Phoenix on Rails blog - Cloudless Studio
Here's an overview, case study and comparison to Phoenix of the V part of Rails MVC as experienced across the years. Rails organizes the view part of the MVC into views and helpers. You are supposed to put templates for each resource/controller into the app/views subdirectories and to put the accompanying helper code into app/helpers which are by default generated per-resource as well. In practice
Rails asset pipeline vs Phoenix and Brunch - Phoenix on Rails blog - Cloudless Studio
Both Rails and Phoenix can manage and deploy assets for you. But the approaches and solutions differ greatly. Development toolsAs a NPM based tool, Brunch recognizes that modern JS is not just jQuery and browser stuff but also a wide choice of development tools. It allows dev-only JavaScript dependencies, just like in mix.deps or Gemfile, so tools like ESLint are no longer second-class citizens. 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
Things I Wish ActiveRecord Had After Using Ecto
A few years ago, I wrote an article about moving from Django to Rails. As I said there, I don’t find it too hard moving from one programming language to another, as long as you have good knowledge on concepts they all share. Each language, of course, brings something on its own. Last year, I decided to try something new. As a Ruby developer, Elixir proved to be a logical choice, and I have to admi
Phoenix for Railsies: Form Helpers and Models — SitePoint
Stay Relevant and Grow Your Career in TechPremium ResultsPublish articles on SitePointDaily curated jobsLearning PathsDiscounts to dev toolsStart Free Trial7 Day Free Trial. Cancel Anytime. Key Takeaways Phoenix, a web framework built for Elixir, is similar to Rails but offers better support for technologies such as WebSockets and can scale better due to being built on the Erlang Virtual Machine.
Incrementally moving to Elixir
Like many working in a legacy Ruby system and learning Elixir we were struggling to figure out how to start moving our code over. Here I wanted to share a technique we used a year ago to start the process. BackgroundAt Fitzdares (a bookmakers) we have an ageing monolith of a system written in Rails over 7 or so years by various teams and contractors and much like the building above it’s starting t
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
連載 Rails2Phoenix 2 認証機能を実装する
連載 Rails2Phoenix 1 UmbrellaプロジェクトをHerokuにデプロイする
Model callbacks in Phoenix, Ecto and Rails - Phoenix on Rails blog - Cloudless Studio
Mistakes Rails Developers Make in Elixir Part 1: Background Jobs - Crevalle
Comparing Rails and Phoenix: Part II
Formatting time ago in words with phoenix
GitHub
Flame
Elvio Vicosa
CSRF protection on single page app API
Explicitness(Ecto) vs Implicitness(Active Record)
Rails and Phoenix microservice synergy