Skip to content
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

Chore: Migrate LiveView Chat App from Heroku to Fly.io #86

Open
6 tasks
nelsonic opened this issue Nov 29, 2022 · 3 comments
Open
6 tasks

Chore: Migrate LiveView Chat App from Heroku to Fly.io #86

nelsonic opened this issue Nov 29, 2022 · 3 comments
Assignees
Labels
chore a tedious but necessary task often paying technical debt help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished T25m Time Estimate 25 Minutes

Comments

@nelsonic
Copy link
Member

Sadly, all "free" Heroku Apps will be deleted this month ... ref: dwyl/learn-heroku#52 🤦‍♂️

Todo

  • Migrate app to liveview-chat.fly.dev
  • Update deployment docs in README.md
  • DELETE any files related to Heroku deployment
  • Add GIF of working App
  • Update URL in repo settings
  • DELETE Heroku App! ✂️
@nelsonic nelsonic added T25m Time Estimate 25 Minutes chore a tedious but necessary task often paying technical debt priority-1 Highest priority issue. This is costing us money every minute that passes. labels Nov 29, 2022
@nelsonic nelsonic self-assigned this Nov 29, 2022
@nelsonic nelsonic changed the title Chore: Migrate Demo App from Heroku to Fly.io Chore: Migrate LiveView Chat App from Heroku to Fly.io Nov 29, 2022
@nelsonic nelsonic added priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished help wanted If you can help make progress with this issue, please comment! and removed priority-1 Highest priority issue. This is costing us money every minute that passes. labels Jan 8, 2023
@LuchoTurtle
Copy link
Member

I've been trying to have a go at this for quite some time.

At first, I was having trouble connecting to the Postgres SQL database due to not having the :ssl configuration present.

** (RuntimeError) SSL connection can not be established because `:ssl` application is not started,
         you can add it to `extra_applications` in your `mix.exs`:

But now I keep getting an error at the end of the deployment phase...

 1 desired, 1 placed, 0 healthy, 1 unhealthy
--> v1 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v2 

Will investigate further, I guess

@nelsonic
Copy link
Member Author

@LuchoTurtle this will need to be updated to the latest Phoenix before it can be deployed to Fly.io ...
Please consider working on this one instead: dwyl/app#312

@LuchoTurtle
Copy link
Member

Pushed #111 nonetheless so anyone can pick up where it was left off 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore a tedious but necessary task often paying technical debt help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished T25m Time Estimate 25 Minutes
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants