-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why? What? Who? How? #1
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or enhancement of existing functionality
good first issue
Good for newcomers
help wanted
If you can help make progress with this issue, please comment!
priority-1
Highest priority issue. This is costing us money every minute that passes.
research
Research required; be specific
spike
The simplest possible experiment to explore potential solutions to a problem
T1d
Time Estimate 1 Day
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
Comments
This was referenced Feb 2, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 3, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 3, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 3, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 3, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 3, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 3, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 6, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 7, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 7, 2023
Just pushed the README sections with the tutorial. Not going to submit it for review yet because I want to:
|
LuchoTurtle
added a commit
that referenced
this issue
Feb 7, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 8, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
LuchoTurtle
added a commit
that referenced
this issue
Feb 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or enhancement of existing functionality
good first issue
Good for newcomers
help wanted
If you can help make progress with this issue, please comment!
priority-1
Highest priority issue. This is costing us money every minute that passes.
research
Research required; be specific
spike
The simplest possible experiment to explore potential solutions to a problem
T1d
Time Estimate 1 Day
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
We are building our backend in
Phoenix
as outlined in: https://github.com/dwyl/technology-stack#phoenixWe need to showcase how to interact with
Phoenix
fromFlutter
in the simplest way possible.Currently
![image](https://user-images.githubusercontent.com/194400/215789702-2028e906-7eb0-47b7-a15e-314b580b5e26.png)
phoenix_socket
: https://pub.dev/packages/phoenix_socketAppears to be the best
<option>
. 💭Although the slow response rate on the open PRs: https://github.com/braverhealth/phoenix-socket-dart/pulls
Is less than reassuring... ⏳
e.g: braverhealth/phoenix-socket-dart#55 should at least have a comment by now ... 🤷♂️
if
you find a better one, please share. 🙏If you get stuck, take a look at: https://github.com/supabase/supabase-flutter#realtime-data-as-stream
Disect their code and if needed (comment first) build our own library to do this!
Todo ✅
it needs to be followed by someone whose time is very scarce so please don't skip any steps ... 🙏
Phoenix
App that has achannel
.UPDATE
our existingphoenix-chat-example
.please see: Chore: Comprehensively Update this Tutorial to
Phoenix v1.7
phoenix-chat-example#149and use that as the basis for this integration.
Flutter
appphoenix_socket
as a dependency.localhost
and attempt to connectFlutter
toPhoenix
.Phoenix
App.Flutter
App.Flutter
app toFly.io
as aPWA
see: SPIKE: Flutter Web Applications learn-flutter#9Flutter
app to https://phoenix-chat.fly.dev to showcase the "Production" version. 🚀That's it.
This should take a couple of days to document & build with tests in both
Phoenix
andFlutter
.Please leave a comment on this issue with
each
step you take in your quest.The resulting repo/demo should be easy for anyone to run.
If you have any questions, please comment.
And if I take longer than
T1h
to respond onGitHub
signal-message me with a direct link to the issue comment.e.g: dwyl/learn-flutter#9 (comment)
The text was updated successfully, but these errors were encountered: