Keep giving us the sauce! It’s clear you really understand the framework and are a first principles thinker. Would love to see a client->db example that shows how state can/should be shared across multiple controllers/views/repos. Maybe some silly multi-player tug-of-war game: players can join a room, each player is assigned a team + or -, once there’s some minimum number of players a countdown starts. After the countdown players mash their respective keys (+ | -) or buttons, there’s some “rope” getting pulled towards the more prolific mashers, once a team the rope fully to their side the lead mashers on the winning team gets to make a leader board entry or update some global state outside the room. Focus would be managing memory vs persistence and how to handle global (leaderboard or whatever) vs selectively shared state (room) vs local state (each players mash count). FWIW, happy to help! Getting deeper into live view/phoenix
Hi Andrew, I watched your "let’s learn the Phoenix Router. And again I am very happy. You answered all the important questions I had so far. So, thanks a lot and congratulations on your style of teaching 🎉
Another very useful video 👌 I might get through all your vids today and tomorrow. Only thing that saddens me is there aren't enough lol. Looking forward to your next uploads
12:15 , is { } braces destructuring or return values are always in braces? i dont know this language, but seems interesting is that language hard to grasp and learn ?
Your videos have been great to get an overview of Phoenix. I'd love to see a video on what managing a live application looks like. You have one that kind of covers dockerising - but what happens once it's deployed? How do you monitor it, and how do you dig into the details. The other bit I'm not clear on is how you would start to think about the non 'Web' modules. So you can just write Elixir code.. but should modules of your application be Genservers or what. Say I want to send an email - should I have an email server running and send it some details. Pretty basic stuff, but I'm just not used to the phoenix (or elixir) way of doing things coming from other full stack frameworks like Laravel or Rails.
That was great thanks! I think you may have saved me some future headaches. Future topic suggestions: JS interop. I know javascript is a dirty word in the phoenix world, but understanding when and how you can use it is often glossed over. And I notice your app.js was actually app.ts! knowing how to switch over would be cool. The other suggestion would be generators. The built in ones (getting the most from them, ie: generate a table and avoid having to fix the migration and schema too much) and how to make your own. Thanks again!
Wow, so much info. Thanks for all this. Maybe you should split your content in smaller video, it was not obvious to me what was included in this router video. Amazing info.
Thanks for the amazing overview! I have a question actually, I know you can add 1-n plugs inside the controller itself, to kinda have some logic to be executed in a plug-like way for this particular controller. Does something like this exist in live views? Or the only place to compose on_mounts is inside the router?
What a awesome vidoe, maybe you can bring us what's the best way to work with nested associations in forms and how to create a CRUD with Liveview without mix phx.gen Thank you for the video.
![[안방1열 직캠4K] 베이비몬스터 치키타 'DRIP' (BABYMONSTER CHIQUITA FanCam) @SBS Inkigayo 241110](http://i.ytimg.com/vi/tnlxo79cAqY/mqdefault.jpg)
I'd love to see more Phoenix videos from you, this is really comprehensive and clear :)
Thank you Taylor!
Keep giving us the sauce! It’s clear you really understand the framework and are a first principles thinker. Would love to see a client->db example that shows how state can/should be shared across multiple controllers/views/repos. Maybe some silly multi-player tug-of-war game: players can join a room, each player is assigned a team + or -, once there’s some minimum number of players a countdown starts. After the countdown players mash their respective keys (+ | -) or buttons, there’s some “rope” getting pulled towards the more prolific mashers, once a team the rope fully to their side the lead mashers on the winning team gets to make a leader board entry or update some global state outside the room. Focus would be managing memory vs persistence and how to handle global (leaderboard or whatever) vs selectively shared state (room) vs local state (each players mash count). FWIW, happy to help! Getting deeper into live view/phoenix
Hi Andrew, I watched your "let’s learn the Phoenix Router.
And again I am very happy. You answered all the important questions I had so far.
So, thanks a lot and congratulations on your style of teaching 🎉
Thank you!
Another very useful video 👌 I might get through all your vids today and tomorrow. Only thing that saddens me is there aren't enough lol. Looking forward to your next uploads
Nice overview about all the router and endpoint modules 💯
Glad you liked it!
Looks like a gold mine. Gonna go through this in detail. Thanks Andrew
Thank you!
Very nicely done! Glad to see some longform Phoenix content on TH-cam.
12:15 , is { } braces destructuring or return values are always in braces?
i dont know this language, but seems interesting
is that language hard to grasp and learn ?
Awesome guide! Thanks for doing 🏋 for us
your video flow is very good. i manage to focus the whole 25mins on phoenix router basics before you talk about phoenix liveview.
Thank you!
Thank you, really fast tho. have to re-watch this informative video
Great video Andrew! A lot of info here! Keep up the good work. Cheers
This overview is a great resource. Thanks Andrew!
Thank you!
Your videos have been great to get an overview of Phoenix. I'd love to see a video on what managing a live application looks like. You have one that kind of covers dockerising - but what happens once it's deployed? How do you monitor it, and how do you dig into the details. The other bit I'm not clear on is how you would start to think about the non 'Web' modules. So you can just write Elixir code.. but should modules of your application be Genservers or what. Say I want to send an email - should I have an email server running and send it some details. Pretty basic stuff, but I'm just not used to the phoenix (or elixir) way of doing things coming from other full stack frameworks like Laravel or Rails.
Awesome stuff man, high quality sh*t, thank you!
Thank you!
That was great thanks! I think you may have saved me some future headaches. Future topic suggestions: JS interop. I know javascript is a dirty word in the phoenix world, but understanding when and how you can use it is often glossed over. And I notice your app.js was actually app.ts! knowing how to switch over would be cool. The other suggestion would be generators. The built in ones (getting the most from them, ie: generate a table and avoid having to fix the migration and schema too much) and how to make your own. Thanks again!
Amazing. I really appreciate what you are doing
Thank you very much!
Wow, so much info. Thanks for all this. Maybe you should split your content in smaller video, it was not obvious to me what was included in this router video. Amazing info.
Thanks for the amazing overview! I have a question actually, I know you can add 1-n plugs inside the controller itself, to kinda have some logic to be executed in a plug-like way for this particular controller. Does something like this exist in live views? Or the only place to compose on_mounts is inside the router?
Yes you can do the exact same thing with on_mount directly in the top level of a LV
What a awesome vidoe, maybe you can bring us what's the best way to work with nested associations in forms and how to create a CRUD with Liveview without mix phx.gen
Thank you for the video.
Thank you, that's a great idea!
You're a life saver 🥹
Thank you!