Learning Elixir, Phoenix and LiveView: A Primer for Experienced Programmers
In order to make web apps with Elixir, here’s a short primer on learning the language and major frameworks: First, don’t just learn Elixir. You can and should learn Elixir and Phoenix at the same time. After getting a hang of Phoenix, jump into LiveView. There is a learning curve to the ecosytem. It’s not particularly steep, but it is longer than a language like go but not as long as required by t
Ecto Getting Started (翻訳) - Qiita
https://hexdocs.pm/ecto/getting-started.html (Ecto v2.0.5) ã®ç¿»è¨³ã«ãªã‚Šã¾ã™ã€‚ 訳ãŒé–“é•ã£ã¦ã„ã‚‹ã€æŠœã‘ã¦ã„ã‚‹ãªã©ã®ç®‡æ‰€ãªã©ã‚’見ã¤ã‘ãŸã‚‰æŒ‡æ‘˜ã—ã¦ã„ãŸã ã‘ã‚‹ã¨åŠ©ã‹ã‚Šã¾ã™ã€‚ ã“ã®ã‚¬ã‚¤ãƒ‰ã¯Elixirã®ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ãƒ©ãƒƒãƒ‘ーåŠã³ã‚¯ã‚¨ãƒªã‚¸ã‚§ãƒãƒ¬ãƒ¼ã‚¿Ectoã¸ã®ã‚¤ãƒ³ãƒˆãƒãƒ€ã‚¯ã‚·ãƒ§ãƒ³ã§ã™ã€‚Ectoã¯ã€Elixirデベãƒãƒƒãƒ‘ーãŒã©ã‚“ãªãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚’使ã£ã¦ã„よã†ã¨åŒã˜ã‚ˆã†ãªæ–¹æ³•ã§ã‚¯ã‚¨ãƒªã«ã‚ˆã‚‹å•ã„åˆã‚ã›ãŒã§ãるよã†ã«ã€æ¨™æº–化ã•ã‚ŒãŸAPIã¨æŠ½è±¡åŒ–ã•ã‚ŒãŸæ–¹æ³•ã‚’æä¾›ã—ã¦ã„ã¾ã™ã€‚ ã“ã®ã‚¬ã‚¤ãƒ‰ã§ã¯ã€PostgreSQLデータベースã®ãƒ¬ã‚³ãƒ¼ãƒ‰ã®ä½œæˆãƒ»èªã¿è¾¼ã¿ãƒ»æ›´æ–°ãƒ»å‰Šé™¤ã®ã‚ˆã†ãªåŸºæœ¬çš„ãªã“ã¨ã«ã¤ã„ã¦å¦ã¹ã¾ã™ã€‚ã‚‚ã—ã“ã®ã‚¬ã‚¤ãƒ‰ä¸ã®ã‚³ãƒ¼ãƒ‰ã‚’見ãŸã‘ã‚Œã°ã€ã“ã“(at ecto/examples/friends on GitHub)ã®ã‚³ãƒ¼ãƒ‰ã‚’見ã¦ãã ã•ã„。 ã“ã®ã‚¬ã‚¤ãƒ‰ã¯äº‹å‰ã«Pos
Replace Callbacks with Ecto.Multi
September 27, 2016 We all have logic in our applications like this: When a user is created, send a notification to an admin When a post is deleted, remove it from the search cache When a password is reset, log out that user’s active sessions These side effects need to be predictable and reliable. Often, they’re some of the key business logic of the whole application. Many Rails applications store
elixir on phoenix ectoを使ã£ã¦ã„ã‚ã„ã‚ãªSELECTæ–‡ - Qiita
# = name = "TEST" User |> where([u], u.name == ^name) |> Repo.all() #SELECT u0.`id`, u0.`name`, u0.`age`, u0.`inserted_at`, u0.`updated_at` FROM `users` AS u0 WHERE (u0.`name` = ?) #["TEST"] # != name = "TEST" User |> where([u], u.name != ^name) |> Repo.all() #SELECT u0.`id`, u0.`name`, u0.`age`, u0.`inserted_at`, u0.`updated_at` FROM `users` AS u0 WHERE (u0.`name` != ?) #["TEST"] # > age = 20 Use
Phoenixã§ã‚·ãƒ¼ãƒ‰ãƒ‡ãƒ¼ã‚¿ã‚’投入ã™ã‚‹ã¨ãã«CSVを使ã„ãŸã„ - Qiita
æ¦‚è¦ å‹•æ©Ÿ 表題ã®é€šã‚Šãªã‚“ã§ã™ãŒã€ã‚‚ã†ã²ã¨ã¤ã€seeds.exs ã«ã¾ã¨ã‚ã¦æ›¸ãã‚“ã˜ã‚ƒãªãã¦ã€ãƒ†ãƒ¼ãƒ–ルã”ã¨ã« Seeder を分割ã—ãŸã„ã€ã¨ã„ã†æ¬²æ±‚ã‚‚ã‚ã‚Šã¾ã™ (ベタ㫠Ecto.Repo.insert!/2 を呼んã§ã‚‚ã„ã„ã—ã€CSVã‹ã‚‰ãƒãƒ¼ãƒ‰ã—ã¦ã‚‚ã„ã„ã—ã€YAML使ã£ã¦ã‚‚ã„ã„ã—ã€ãƒ†ãƒ¼ãƒ–ルã”ã¨ã«ã‚¹ãƒˆãƒ©ãƒ†ã‚¸ãƒ¼ã‚’変ãˆã‚‰ã‚Œã‚‹ã‚ˆã†ã«ã‚‚ã—ãŸã„ã®ã§)。 ã¨ã«ã‹ã Elixir 始ã‚ãŸã°ã‹ã‚Šãªã®ã§ã€ã‚‚ã£ã¨ã„ã„方法ã‚るよã€ã¨ã„ã†ã®ãŒã‚ã£ãŸã‚‰æ•™ãˆã¦ã„ãŸã ã‘ã‚‹ã¨åŠ©ã‹ã‚Šã¾ã™ã€‚ 環境 Elixir 1.3.1 Erlang/OTP 18 [erts-7.3] Phoenix 1.2.0 ã‚„ã£ãŸã“㨠CSVファイルをèªã‚“ã§ã€è¡Œã”ã¨ã« Ecto.Repo.insert!/2 を実行ã™ã‚‹ ã¡ãªã¿ã«ä¸€èˆ¬çš„ãªã‚„ã‚Šæ–¹ã¯â€¦ 調ã¹ãŸé™ã‚Šã€priv/repo/seeds.exs ã« Ecto.Repo.insert!/2 書ã„ã¦ã„
Using Ecto 2, without Phoenix, but with tests
My guess is that the majority of people using Ecto are using it from Phoenix. Through Phoenix Ecto, they get a lot of the boilerplate code generated for them. Using Ecto by itself, means that you need to deal with that boilerplate. There are a couple of reasons that you would want to use Ecto this way. The most obvious is that you are writing something without a web frontend, but that needs databa
Phoenix v1.3ã‹ã‚‰ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªæ§‹æˆãŒå¤‰ã‚ã‚‹ã£ã½ã„ - mmag
※ 多分ã«æŽ¨æ¸¬ãŒå«ã¾ã‚Œã¦ã„ã¾ã™ã€‚ã‚ã¨ã§ã¡ã‚ƒã‚“ã¨èª¿ã¹ãªã„㨠※ 今ã¾ã•ã«æµ·ã®å‘ã“ã†ã§ã¯Elixir & Phoenix Conf 2016ãŒè¡Œã‚ã‚Œã¦ã„ã‚‹ã®ã§ã™ãŒã€ã‚¤ãƒ³ã‚¿ãƒãƒƒãƒ„を通ã—ã¦ã“ã‚“ãªãƒ„イートãŒæµã‚Œã¦ãã¾ã—ãŸã€‚ Coming in Phoenix 1.3 #elixirconf @elixirphoenix #myelixirstatus pic.twitter.com/oeq877IOVA— Dorian Karter (@dorian_escplan) 2016å¹´9月1æ—¥ ä»–ã®ãƒ„イートを探ã—ã¦ã„ãã¨ã€Phoenix 1.3ã§ã¯webディレクトリãŒlib/my_app/webã®ã‚ˆã†ã«lib以下ã¸å…¥ã‚‹ã¨ã®ã“ã¨ã€‚ . ├── assets ├── config ├── lib │  └── my_app │  └── web │  ├── channels │  ├── contr
Phoenixã®timestampsã®ã‚«ãƒ©ãƒ åを変更ã™ã‚‹
Railsã§ä½œã£ãŸDBã¸Phoenixã§æŽ¥ç¶šã™ã‚‹ã¨ãã®timestampsã®ã‚«ãƒ©ãƒ å変更方法． mix ecto.generate 㧠model を作るã¨ä»¥ä¸‹ã®ã‚ˆã†ãªå½¢å¼ã«ãªã‚‹ï¼Žã“ã®ã¨ã timestamps ã¯ä½•ã‚‚指定ã—ãªã‘れ㰠inserted_at 㨠updated_at ã¨ã„ã†ã‚«ãƒ©ãƒ を指ã™ï¼Ž 一方，Railsã® timestamp 㯠created_at 㨠updated_at ãªã®ã§ï¼Œã“ã®ã¾ã¾ phoenix ã‚’å‹•ã‹ã™ã¨DBã«ã¯ inserted_at ã¨ã„ã†ã‚«ãƒ©ãƒ ãŒè¦‹ã¤ã‹ã‚‰ãªã„ã¨ã„ã†ã‚¨ãƒ©ãƒ¼ã«ãªã‚‹ï¼Ž defmodule MySampleApp.User do use FarmnoteAdminConsole.Web, :model schema "users" do field :name, :string timestamps end # (ç•¥) end ã“れを回é¿ã™ã‚‹
Connecting to Multiple Databases with Ecto
Geoffrey Lessel Author of Phoenix in Action. Developer at Planning Center. Slowly learning about living in California. You can call me Geo. Now that we’ve explored some simple Ecto setups, let’s get a little bit exotic. Did you know that you can set up your application in such a way that you can connect to multiple databases with Ecto? Ecto actually makes it super simple to do so. Let’s take a loo
Folding Window Functions Into Ecto
Folding Window Functions Into Ecto 08 Feb 2016 by Parker Selbert This is a reinterpretation of Folding Window Functions Into Rails, rewritten and adapted from ActiveRecord to Ecto 2.0. The results were unexpected… Perhaps you’ve heard of window functions in PostgreSQL, but you aren’t quite sure what they are or how to use them. On the surface they seem esoteric and their use-cases are ambiguous. S
複数ã®Ecto.Multiを一ã¤ã®ãƒˆãƒ©ãƒ³ã‚¶ã‚¯ã‚·ãƒ§ãƒ³å†…ã§å®Ÿè¡Œã™ã‚‹ã«ã¯ï¼Ÿ - Qiita
defmodule MyApp.EntryService do def insert(params) do Ecto.Multi.new |> Ecto.Multi.insert(:entry, Entry.changeset(%Entry{}, params)) |> Ecto.Multi.insert(:log, Log.changeset(%Log{}, event: "entry inserted")) end end defmodule MyApp.SectionService do def insert(params) do Ecto.Multi.new |> Ecto.Multi.insert(:section, Entry.changeset(%Section{}, params)) |> Ecto.Multi.insert(:log, Log.changeset(%Log
priv/repo/migrationsãŒç„¡ãã¦ãƒ†ã‚¹ãƒˆã‚‚ã§ããªã‹ã£ãŸ - mmag
昨日ã¯Phoenixアプリをã¡ã‚‡ã£ã¨æ›¸ã„ãŸã‚¨ãƒ³ãƒˆãƒªã‚’書ãã¾ã—ãŸã€‚ ãã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã¯ç§ç‰©ã®PCã§phoenix newã—ã¦ç”Ÿæˆã—ãŸã‚‚ã®ãªã®ã§ã™ãŒã€ä¼šç¤¾ã®PCã§git cloneã—ã¦mix testã¨ã‚„ã£ãŸã‚‰ä½•ã‹ã‚¨ãƒ©ãƒ¼ã€‚ ** (Mix) Could not find migrations directory "priv/repo/migrations" for repo PhMicroblog.Repo ã“れをサッã¨èªã‚“ã§ã€ç‰¹ã«ä½•ã‚‚考ãˆãšã«kill。ãã£ã¨ä»¥å‰åŒã˜ã‚ˆã†ãªã“ã¨ãŒã‚ã£ã¦ã€å†èµ·å‹•ã—ãŸã‚‰ã‚¤ã‚±ãŸã®ã§ã—ょã†ã€‚ 躊躇ã†ã“ã¨ãªãè¡Œã‚れる殺戮(kill)。ã—ã‹ã—生ã返る巨åƒ(postgres)。繰り返ã•ã‚Œã‚‹ä¸ç¾©(kill)。神(launchctl)ã¯æ»ã¬ã“ã¨ã‚’許ã•ã¬ã®ã 。ãªã‚“ã¨ç„¡æ…ˆæ‚²ãªã€‚ 10秒ã»ã©éžé“ã‚’è¡Œã£ãŸå¾Œã€å†åº¦ã‚¨ãƒ©ãƒ¼ã«ç›®ã‚’やる㨠... Could not find migratio
Phoenixガイドラインをèªã‚“ã§ã¿ãŸ(9) - Ecto - - Qiita
ã¯ã˜ã‚ã« å‰å›žã¯ã€Channelを見ã¦ãã¾ã—ãŸã€‚ 今回ã¯Ectoã€ãã†DBã§ã™ã€‚ 外㸠多ãã®ã‚¢ãƒ—リケーションã§ã¯ãƒ‡ãƒ¼ã‚¿ã‚¹ãƒˆãƒ¬ãƒ¼ã‚¸ã¸ã®ã‚¢ã‚¯ã‚»ã‚¹ãŒå¿…è¦ã¨ã•ã‚Œã¦ã„ã¾ã™ã€‚Elixirã§ã¯Ectoを使ã£ã¦ãƒ‡ãƒ¼ã‚¿ã‚¢ã‚¯ã‚»ã‚¹ã‚’è¡Œã†ã“ã¨ãŒå¯èƒ½ã§ã™ã€‚Ectoã«ã¯ã€ç¾åœ¨ä»¥ä¸‹ã®ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã¸ã®ã‚¢ãƒ€ãƒ—ã‚¿ãŒå˜åœ¨ã—ã¾ã™ã€‚ PostgreSQL MySQL MSSQL SQLite3 MongoDB Phoenixã§ã¯ã€æ¨™æº–ã§ã€Ectoã¨PostgreSQLã®ã‚¢ãƒ€ãƒ—ã‚¿ãŒã‚»ãƒƒãƒˆã•ã‚Œã¦ã„ã¾ã™ã€‚ 以後ã€Ectoã¨Postgrex(Elixirã®PostgreSQLドライãƒ)ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã€è¨å®šãŒå®Œäº†ã—ã¦ã„ã‚‹ã¨ã—ã¾ã™ã€‚ Ectoã§ã¯ã€phoenix.gen.htmlを使ã£ã¦ãƒªã‚½ãƒ¼ã‚¹ã‚’生æˆã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ã“ã“ã§ã¯ã€Userリソース(フィールドã¨ã—ã¦name, email, bio, number_of_pets)を作る
Phoenix/Ectoã§ãƒ¢ãƒ‡ãƒ«ã®å¤šè¨€èªžåŒ–ã«å¯¾å¿œã™ã‚‹æ–¹æ³• - Qiita
Phoenixã«ãŠã‘ã‚‹Viewã®å¤šè¨€èªžåŒ–ã¯Gettextを使ã†æ–¹æ³•ãŒã‚¹ã‚¿ãƒ³ãƒ€ãƒ¼ãƒ‰ã§ã™ãŒã€Railsã®globalizeã®ã‚ˆã†ãªã€ãƒ¢ãƒ‡ãƒ«ã®å¤šè¨€èªžåŒ–ã«å¯¾å¿œã™ã‚‹ãŸã‚ã®ãƒ‘ッケージãŒElixir/Phoenixã«ã¯ã¾ã å˜åœ¨ã—ã¦ã„ã¾ã›ã‚“。 ã¨ã„ã†ã“ã¨ã§ã€ä½œã£ã¦ã¿ã¾ã—ãŸã€‚ translator (ã¡ãªã¿ã«Ecto2.0以上é™å®šã«ãªã‚Šã¾ã™) 使用方法 下記ã®ã‚ˆã†ãªUserモデルã®ã€nameã¨profile列を多言語化ã™ã‚‹æ‰‹é †ã«ã¤ã„ã¦èª¬æ˜Žã—ã¾ã™ã€‚ defmodule MyApp.User do use MyApp.Web, :model schema "users" do field :email, :string field :name, :string field :profile, :string timestamps end @required_fields ~w(email name)a @opt
What's new in Ecto 2.1 (Free eBook)
What's new in Ecto 2.1Â FREE ebook In 11 chapters, this ebook explains how to use Ecto as a data-centric tool and its new features: Ecto is not your ORM A look into ORMs and what sets Ecto apart Schemaless queries Keep the database at your fingertips without the need to intermediate all operations through schemas Schemas and changesets Cast, validate and control changes to any schema or struct, ind
Ecto for Rails developers — The basics - Rendered Text
We at Rendered Text are huge fans of Ruby on Rails. As a proof, SemaphoreCI — our biggest product — is still mostly written in Ruby. Lately, however, we started migrating toward Elixir and the OTP platform. Erlang has an excellent platform for developing giant, scalable and fault tolerant systems. Elixir, on the other hand, is a Ruby-like language that helped us to swiftly transition parts of our
ランã‚ング
ランã‚ング
障害
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
tokyo_ex_6.key
Ecto用ã®state machine - Qiita
Ecto 2.0 ã«å¯¾å¿œã—㟠changeset/2 ã®æ›¸ãæ–¹ - Qiita
Combining an Ecto Model with an Arc Uploader in Elixir
{{#tags}}- {{label}}
{{/tags}}